Skip to content

Instantly share code, notes, and snippets.

@mdmower
mdmower / autocomplete-script-bind-example.html
Created February 15, 2020 07:28
amp-autocomplete + amp-bind + amp-script testing
<!DOCTYPE html>
<html ⚡>
<head>
<meta charset="utf-8">
<title>autocomplete testing</title>
<link rel="canonical" href="autocomplete-testing.html" >
<meta name="viewport" content="width=device-width,initial-scale=1">
<style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
<script async src=
[09:01:18] Using gulpfile ~/source/amphtml/gulpfile.js
[09:01:18] Starting 'unit'...
[09:01:18] Run gulp help to see a list of all test flags.
[09:01:18] ⤷ Use --nohelp to silence these messages.
[09:01:18] ⤷ Use --local_changes to run unit tests from files commited to the local branch.
[09:01:18] ⤷ Use --testnames to see the names of all tests being run.
[09:01:18] Running tests against minified code.
[09:01:18] --headless: Running tests in a headless Chrome window.
[09:01:19] All packages in node_modules are up to date.
[09:01:21] Recompiled all CSS files into build/ (2.577 s)
[09:50:00] Using gulpfile ~/source/amphtml/gulpfile.js
[09:50:00] Starting 'unit'...
[09:50:00] Run gulp help to see a list of all test flags.
[09:50:00] ⤷ Use --nohelp to silence these messages.
[09:50:00] ⤷ Use --local_changes to run unit tests from files commited to the local branch.
[09:50:00] ⤷ Use --testnames to see the names of all tests being run.
[09:50:00] Running tests against minified code.
[09:50:00] --headless: Running tests in a headless Chrome window.
[09:50:00] All packages in node_modules are up to date.
[09:50:03] Recompiled all CSS files into build/ (2.767 s)
@mdmower
mdmower / amphtml-verbose-unit-tests.log
Created February 23, 2020 17:15
AMPHTML verbose unit tests - 2020-02-22
This file has been truncated, but you can view the full file.
[14:00:08] Using gulpfile ~/source/amphtml/gulpfile.js
[14:00:08] Starting 'unit'...
[14:00:08] Run gulp help to see a list of all test flags.
[14:00:08] ⤷ Use --nohelp to silence these messages.
[14:00:08] ⤷ Use --local_changes to run unit tests from files commited to the local branch.
[14:00:08] ⤷ Use --testnames to see the names of all tests being run.
[14:00:08] Running tests against unminified code.
[14:00:08] --headless: Running tests in a headless Chrome window.
[14:00:08] --nobuild: Skipping build.
[14:00:08] --verbose: Enabling verbose mode. Expect lots of output!
@mdmower
mdmower / ampdoc-impl.js
Created February 26, 2020 06:39
Cached meta
/**
* Copyright 2016 The AMP HTML Authors. All Rights Reserved.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
@mdmower
mdmower / hosting-amp-framework.md
Last active October 26, 2021 23:22
Hosting the AMP framework

Documentation Moved
This guide is now available from the AMP Project at:
https://github.com/ampproject/amphtml/blob/main/docs/spec/amp-framework-hosting.md
No further updates are planned for this gist, so please use the official documentation going forward.

Hosting the AMP framework

You can host the AMP framework and components from your own server or CDN. This feature has a number of applications. For example, you can...

  • set a release cadence that matches your development cycle.
@mdmower
mdmower / logwatch-sshd-conf.patch
Last active November 20, 2020 06:54
Logwatch modifications to avoid Google Mail (GMail) spam detection
diff --git a/etc/logwatch/conf/services/sshd.conf b/etc/logwatch/conf/services/sshd.conf
new file mode 100644
index 0000000..a346169
--- /dev/null
+++ b/etc/logwatch/conf/services/sshd.conf
@@ -0,0 +1,2 @@
+# Set to No to disable IP lookups
+$sshd_ip_lookup = No
@mdmower
mdmower / gstreamer-mr2928-gst-plugins-base10.patch
Created November 11, 2022 19:20
gstreamer mr2928 / gst-plugins-base1.0 part
From 3dd1f8ece2ef57d1678f7c074a7dad170744d081 Mon Sep 17 00:00:00 2001
From: Philipp Zabel <p.zabel@pengutronix.de>
Date: Wed, 28 Mar 2018 17:54:15 +0200
Subject: [PATCH] buffer: drop parent meta in deep copy/foreach_metadata
The purpose of a deep buffer copy is to be able to release the source
buffer and all its dependencies. Attaching the parent buffer meta to
the newly created deep copy needlessly keeps holding a reference to the
parent buffer.
@mdmower
mdmower / gstreamer-mr2928-gstreamer10.patch
Created November 11, 2022 19:22
gstreamer mr2928 / gstreamer1.0 part
From 1f35211c952801709edef60276851ebdb1d3908c Mon Sep 17 00:00:00 2001
From: Philipp Zabel <p.zabel@pengutronix.de>
Date: Wed, 28 Mar 2018 17:54:15 +0200
Subject: [PATCH] buffer: drop parent meta in deep copy/foreach_metadata
The purpose of a deep buffer copy is to be able to release the source
buffer and all its dependencies. Attaching the parent buffer meta to
the newly created deep copy needlessly keeps holding a reference to the
parent buffer.