featCommits, that adds or remove a new featurefixCommits, that fixes a bugrefactorCommits, that rewrite/restructure your code, however does not change any API behaviourperfCommits are specialrefactorcommits, that improve performancestyleCommits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc)testCommits, that add missing tests or correcting existing testsdocsCommits, that affect documentation onlybuildCommits, that affect build components like build tool, ci pipeline, dependencies, project version, ...opsCommits, that affect operational components like infrastructure, deployment, backup, recovery, ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/usr/bin/env ruby | |
| # deep_research.rb | |
| require 'openai' | |
| require 'json' | |
| require 'net/http' | |
| require 'uri' | |
| require 'timeout' | |
| require 'time' |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| import android.util.Log | |
| import io.ktor.util.decodeBase64Bytes | |
| import io.ktor.util.encodeBase64 | |
| import okhttp3.OkHttpClient | |
| import okhttp3.Request | |
| import okhttp3.Response | |
| import okhttp3.WebSocket | |
| import okhttp3.WebSocketListener | |
| import okio.ByteString | |
| import org.json.JSONArray |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| package main | |
| import ( | |
| "fmt" | |
| "reflect" | |
| ) | |
| // Name of the struct tag used in examples | |
| const tagName = "validate" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| function downloadFile(url) { | |
| var loaded = $.Deferred(); | |
| var request = new XMLHttpRequest(); | |
| request.open('GET', url); | |
| // ! setting the responseType has to be after the `request.open` | |
| // `arraybuffer` is necessary for Internet Explorer and Edge becuase | |
| // they do not support `blob` as response type | |
| request.responseType = "arraybuffer"; | |
| request.onload = function() { |
The difference between XYZ and TMS tiles and how to convert between them
Lots of tile-based maps use either the XYZ or TMS scheme. These are the maps that have tiles
ending in /0/0/0.png or something. Sometimes if it's a script, it'll look like
&z=0&y=0&x=0 instead. Anyway, these are usually maps in Spherical Mercator.
Good examples are OpenStreetMap, Google Maps, MapBox, MapQuest, etc. Lots of maps.
Most of those are in XYZ. The best documentation for that is slippy map tilenames on the OSM Wiki, and Klokan's Tiles a la Google.