| PREFIX wd: <http://www.wikidata.org/entity/> | |
| PREFIX wdt: <http://www.wikidata.org/prop/direct/> | |
| PREFIX wikibase: <http://wikiba.se/ontology#> | |
| PREFIX p: <http://www.wikidata.org/prop/> | |
| PREFIX v: <http://www.wikidata.org/prop/statement/> | |
| PREFIX q: <http://www.wikidata.org/prop/qualifier/> | |
| PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> | |
| SELECT ?s ?sLabel ?lLabel ?geo { | |
| ?s wdt:P31 wd:Q1565828 . |
Should be work with 0.18
Destructuring(or pattern matching) is a way used to extract data from a data structure(tuple, list, record) that mirros the construction. Compare to other languages, Elm support much less destructuring but let's see what it got !
myTuple = ("A", "B", "C")
myNestedTuple = ("A", "B", "C", ("X", "Y", "Z"))
| import xml | |
| import xml.etree.ElementTree as ET | |
| from collections import defaultdict | |
| PREFIX = defaultdict(lambda: "Svg.Attributes") | |
| #PREFIX['href'] = 'Html.Attributes' | |
| def open_file(filename): | |
| with open(filename) as f: |
GitHub repositories can disclose all sorts of potentially valuable information for bug bounty hunters. The targets do not always have to be open source for there to be issues. Organization members and their open source projects can sometimes accidentally expose information that could be used against the target company. in this article I will give you a brief overview that should help you get started targeting GitHub repositories for vulnerabilities and for general recon.
You can just do your research on github.com, but I would suggest cloning all the target's repositories so that you can run your tests locally. I would highly recommend @mazen160's GitHubCloner. Just run the script and you should be good to go.
$ python githubcloner.py --org organization -o /tmp/output
If you're thinking of checking out the Pony programming language, here's a list of things that I think are important to know. This list is based on a Tweet that I wrote.
There are Pony packages for several popular editors.
| // funciona somente com v3.1.6, essa estrategia de end/continue | |
| // era um backdoor para fazer recursao em types, recursao funcionava somente com interfaces | |
| // antigamente pela resolucao de tipos ser lazyness e nao acabar fazendo o compiler cair | |
| // potencialmente em um looping infinito na resolucao do tipo, por causa disto tem validacao | |
| // no compiler agora e codigos nesse estilo sao barrados pelo compiler | |
| type Init<T extends any[], TTail extends any[] = TailArray<T>> = CastArray<{ | |
| [K in keyof TTail]: T[keyof T & K]; | |
| }> |