JMS: only java, it is a specification
AMPQ: universal, it is a protocol, it is open standard for messaging
JMS doesn't define a protocol.
JMS is an API and AMQP is a protocol.
AMQP supports 4 message models: Direct, Fanout, Topic, Headers
''' | |
Freezing a stable-baselines to a frozen protocol buffer file to be served. | |
https://github.com/hill-a/stable-baselines | |
Some code taken from this lovely blog series | |
https://blog.metaflow.fr/tensorflow-how-to-freeze-a-model-and-serve-it-with-a-python-api-d4f3596b3adc | |
''' | |
import tensorflow as tf | |
import os |
/** | |
* utilities to do sigv4 | |
* @class SigV4Utils | |
*/ | |
function SigV4Utils() {} | |
SigV4Utils.getSignatureKey = function (key, date, region, service) { | |
var kDate = AWS.util.crypto.hmac('AWS4' + key, date, 'buffer'); | |
var kRegion = AWS.util.crypto.hmac(kDate, region, 'buffer'); | |
var kService = AWS.util.crypto.hmac(kRegion, service, 'buffer'); |
""" Trains an agent with (stochastic) Policy Gradients on Pong. Uses OpenAI Gym. """ | |
import numpy as np | |
import cPickle as pickle | |
import gym | |
# hyperparameters | |
H = 200 # number of hidden layer neurons | |
batch_size = 10 # every how many episodes to do a param update? | |
learning_rate = 1e-4 | |
gamma = 0.99 # discount factor for reward |
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j