esafwan

IMPORTANT

zdict parameter and keyword argument support added in v3.3. Use python3.

Refences:

1. https://docs.python.org/3/library/zlib.html#zlib.compressobj
2. https://stackoverflow.com/questions/37499818/python-3-4-zlib-deflate-and-shared-dict
3. https://golang.org/pkg/compress/flate/#example__dictionary

alirezamika

Grouping results and removing unwanted ones

Here we want to scrape product name, price and rating from ebay product pages:

url = 'https://www.ebay.com/itm/Sony-PlayStation-4-PS4-Pro-1TB-4K-Console-Black/203084236670' 

wanted_list = ['Sony PlayStation 4 PS4 Pro 1TB 4K Console - Black', 'US $349.99', '4.8'] 

scraper.build(url, wanted_list)

lu4nm3

use futures::StreamExt;
use std::error::Error;
use tokio;
use tokio::macros::support::Pin;
use tokio::prelude::*;
use tokio::time::{Duration, Instant};

pub fn main() -> Result<(), Box<dyn std::error::Error>> {
    let mut multi_threaded_runtime = tokio::runtime::Builder::new()
        .threaded_scheduler()

PhilippeBoisney

cd ~/Library/Android/sdk/platform-tools/

# Get the hash of the mitmproxy-ca certificate.
openssl x509 -inform PEM -subject_hash_old -in ~/.mitmproxy/mitmproxy-ca.pem | head -1

# We will use this hash value, append '.0' (dot zero) and use this as the filename for the resulting Android certificate
cat ~/.mitmproxy/mitmproxy-ca.pem > c8750f0d.0
openssl x509 -inform PEM -text -in ~/.mitmproxy/mitmproxy-ca.pem -out /dev/null >> c8750f0d.0

# In an other terminal, we will start the emulator with writable /system volume

mingalevme

class GoogleMapsQueryArgsDeserializer
{
    public static function deserialize(string $input): array
    {
        $params = explode('!', trim($input, '!'));

        foreach ($params as $i => $param) {
            $params[$i] = urldecode($param);
        }

export-mike

[{
  "code": "ac_refrigeration_repair",
  "value": "7623",
  "name": "A/C Refrigeration Repair"
},
{
  "code": "accounting_bookkeeping_services",
  "value": "8931",
  "name": "Accounting/Bookkeeping Services"
},

bvaughn

This API was removed in React 17

---

Interaction tracing with React

React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".

With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.

a7v8x

 query IntrospectionQuery {
    __schema {
      queryType { name }
      mutationType { name }
      types {
        ...FullType
      }
      directives {
        name
        description

ibrahima

import React from 'react';
import PropTypes from 'prop-types';
import SyntaxHighlighter from 'react-syntax-highlighter';

export default class CodeBlock extends React.PureComponent {
  static propTypes = {
    value: PropTypes.string.isRequired,
    language: PropTypes.string,
  }

swalkinshaw

Moved to Shopify/graphql-design-tutorial