See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
# Try it out by opening https://ide.kaitai.io/ and copying this file there | |
# Based on an article by @angelcarve about ESP8266 binary image parsing with Kaitai Struct: | |
# https://carvesystems.com/news/parsing-binaries-with-kaitai-struct/ | |
meta: | |
id: esp | |
file-extension: bin | |
endian: le | |
seq: |
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
#get apks from server? wget -np -e robots=off -m site.com/apk/folder/ | |
#Place all apks in the same dir as py file or change os.listdir parameter | |
#you can get del.js from my repo https://github.com/eybisi/fridaScripts/blob/master/del.js | |
import os | |
from androguard.core.bytecodes import apk | |
import frida | |
import time | |
device = frida.get_usb_device() | |
files = [f for f in os.listdir("./")] | |
for f in files: |
SELECT table, | |
formatReadableSize(sum(bytes)) as size, | |
min(min_date) as min_date, | |
max(max_date) as max_date | |
FROM system.parts | |
WHERE active | |
GROUP BY table |
The sony bravia has a HTTP API interacted with using a Pre-Shared key. There's a more complex auth flow but I've not described it here.
There wasn't any documentation, so I've written some. If you're a TV integrator don't read this, you'll laugh. I'm probably just getting confused by UPnP.
Disclaimer: I've only tested this on my TV, which is a KDL-50W829B. Your TV might not have all of the services; see Available services section for how to discover what your TV supports.
# download | |
aria2c -x 5 -i file.m3u8 | |
# decode (example) | |
openssl aes-128-cbc -d -K 15D0F46608409DA364E3F5D92BDE9F61 -iv 00000000000000000000000000000000 -nosalt -in G00000000.ts -out G00000000.d.ts | |
# join all ts files | |
cat *.ts > out.ts | |
# convert ts output file |
Using py.test is great and the support for test fixtures is pretty awesome. However, in order to share your fixtures across your entire module, py.test suggests you define all your fixtures within one single conftest.py
file. This is impractical if you have a large quantity of fixtures -- for better organization and readibility, you would much rather define your fixtures across multiple, well-named files. But how do you do that? ...No one on the internet seemed to know.
Turns out, however, you can define fixtures in individual files like this:
tests/fixtures/add.py
import pytest
@pytest.fixture
Grails Help | |
http://grails.asia/grails-tutorial-for-beginners-setup-your-windows-development-environment/ | |
Decompiling Groovy | |
http://michael.laffargue.fr/blog/2013/11/02/decompiling-groovy-made-classes/ | |
InvokeDynamic | |
http://mydailyjava.blogspot.in/2015/03/dismantling-invokedynamic.html | |
https://docs.oracle.com/javase/8/docs/technotes/guides/vm/multiple-language-support.html | |
http://niklasschlimm.blogspot.in/2012/02/java-7-complete-invokedynamic-example.html |
dummy |
from __future__ import print_function | |
from collections import OrderedDict | |
from prepareable import Prepareable | |
from six import with_metaclass, iteritems | |
class FooMeta(with_metaclass(Prepareable, type)): | |
def __new__(cls, name, bases, attributes): |