The example code does not work as intended.

Steps to reproduce

Use the example code:

var express = require('express');
var proxy = require('http-proxy-middleware');

var app = express();

app.use(
  '/api',
  proxy({ target: 'http://www.example.org', changeOrigin: true })
);
app.listen(3000);

Expected behavior

This should create a proxy for /api to `http

uploadTimeout option defaults to 60000 in the source code, which is missing from the list of options specified in README.md file.

Something based on https://docs.djangoproject.com/en/3.0/howto/upgrade-version/ would be a good idea.

• Review the change log for breaking changes
• Upgrade one feature release at a time (eg 2.2.x to 2.3.x)
• Test for deprecation warnings before/after each feature release
• Suggestion to run ./manage.py djstripe_sync_models after feature release in order to populate new fields - link to h

getting the following error message.

ksql> CREATE STREAM CUSTOMERS_SRC WITH (KAFKA_TOPIC='asgard.public.customers', VALUE_FORMAT='AVRO'); Avro schema for message values on topic asgard.public.customers does not exist in the

ssh-connect is not working for zsh environment with extended_history flag enabled, because it's changing $HISTFILE format. From the docs:

EXTENDED_HISTORY
Save each command’s beginning timestamp (in seconds since the epoch) and the duration (in seconds) to the history file. The format of this prefixed data is:

We should add some linting to the pipeline to help us catch issues with the code.

golangci-lint seems like a good choice, but I'm interested to hear if there are any other preferences before implementing this.