The privacy details that you may need to add for Apple Privacy Manifest.
This config plugin it's already available from expo >=50.0.17 (Part of this PR by aleqsio)
Tip
Read more about Privacy Manifest File from Apple docs
# Usage: git total [OPTION...] | |
# | |
# Options: | |
# | |
# In theory, the command accepts all command line options supported by | |
# the "git log" command. In reality, however, only few commit-limiting | |
# options are useful. This includes: | |
# | |
# --author=PATTERN, --committer=PATTERN | |
# Displays the number of lines changed by a certain author. |
int main() | |
{ | |
printf("hello world"); | |
return 0; | |
} |
// JS array equivalents to C# LINQ methods - by Dan B. | |
// First: This version using older JavaScript notation for universal browser support (scroll down for ES6 version): | |
// Here's a simple array of "person" objects | |
var people = [ | |
{ name: "John", age: 20 }, | |
{ name: "Mary", age: 35 }, | |
{ name: "Arthur", age: 78 }, | |
{ name: "Mike", age: 27 }, |
The privacy details that you may need to add for Apple Privacy Manifest.
This config plugin it's already available from expo >=50.0.17 (Part of this PR by aleqsio)
Tip
Read more about Privacy Manifest File from Apple docs
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
, elem.offsetTop
, elem.offsetWidth
, elem.offsetHeight
, elem.offsetParent
// To ensure cross-browser support even without a proper SubtleCrypto | |
// impelmentation (or without access to the impelmentation, as is the case with | |
// Chrome loaded over HTTP instead of HTTPS), this library can create SHA-256 | |
// HMAC signatures using nothing but raw JavaScript | |
/* eslint-disable no-magic-numbers, id-length, no-param-reassign, new-cap */ | |
// By giving internal functions names that we can mangle, future calls to | |
// them are reduced to a single byte (minor space savings in minified file) | |
var uint8Array = Uint8Array; |
from __future__ import print_function | |
import requests | |
import json | |
import cv2 | |
addr = 'http://localhost:5000' | |
test_url = addr + '/api/test' | |
# prepare headers for http request | |
content_type = 'image/jpeg' |
import os, time | |
from itertools import combinations | |
import numpy as np | |
import matplotlib.pyplot as plt | |
from IPython.display import clear_output | |
class NonogramSolver: | |
def __init__(self, ROWS_VALUES=[[2], [4], [6], [4, 3], [5, 4], [2, 3, 2], [3, 5], [5], [3], [2], [2], [6]], COLS_VALUES=[[3], [5], [3, 2, 1], [5, 1, 1], [12], [3, 7], [4, 1, 1, 1], [3, 1, 1], [4], [2]], savepath=''): | |
self.ROWS_VALUES = ROWS_VALUES | |
self.no_of_rows = len(ROWS_VALUES) |
This logging setup configures Structlog to output pretty logs in development, and JSON log lines in production.
Then, you can use Structlog loggers or standard logging
loggers, and they both will be processed by the Structlog pipeline (see the hello()
endpoint for reference). That way any log generated by your dependencies will also be processed and enriched, even if they know nothing about Structlog!
Requests are assigned a correlation ID with the asgi-correlation-id
middleware (either captured from incoming request or generated on the fly).
All logs are linked to the correlation ID, and to the Datadog trace/span if instrumented.
This data "global to the request" is stored in context vars, and automatically added to all logs produced during the request thanks to Structlog.
You can add to these "global local variables" at any point in an endpoint with `structlog.contextvars.bind_contextvars(custom