Skip to content

Commit dce9cb0

Browse files
committed
Remove google ads
1 parent 26650ba commit dce9cb0

10 files changed

+2
-24
lines changed

docs/_posts/2016-11-03-pipe-jq-to-less.markdown

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,6 @@ Or shorthand:
1616
jq -C . data.json | less -R
1717
```
1818

19-
{% include google_in_article.html %}
20-
2119
From the [jq documentation](https://stedolan.github.io/jq/manual/#Invokingjq):
2220
```
2321
--color-output / -C

docs/_posts/airflow/2017-10-20-testing-dags.markdown

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,6 @@ To test the operator, first instantiate three objects:
3131

3232
Then call the execute method.
3333

34-
{% include google_in_article.html %}
35-
3634
## The Test
3735

3836
```python

docs/_posts/airflow/2017-12-13-airflows-execute-context.markdown

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,6 @@ Airflow's context dictionary can be found in the `get_template_context` method,
1616
in Airflow's
1717
[models.py](https://github.com/databricks/incubator-airflow/blob/master/airflow/models.py).
1818

19-
{% include google_in_article.html %}
20-
2119
```python
2220
{
2321
'dag': task.dag,

docs/_posts/airflow/2018-01-12-generate-fernet-key.markdown

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,6 @@ $ python -c "from cryptography.fernet import Fernet; print(Fernet.generate_key()
2323
81HqDtbqAywKSOumSha3BhWNOdQ26slT6K0YaZeZyPs=
2424
```
2525

26-
{% include google_in_article.html %}
27-
2826
## Use a fernet key with Airflow
2927

3028
Paste the key into your `airflow.cfg`.

docs/_posts/airflow/2018-03-05-run-dag-and-watch-logs.markdown

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,6 @@ SequentialExecutor), but it won't work in production because issues
3838
will arise when multiple tasks attempt to write to the same log file at once.
3939
</div>
4040

41-
{% include google_in_article.html %}
42-
4341
## Easy Solution
4442

4543
<div class="warning" markdown="1">
@@ -83,8 +81,6 @@ Edit airflow_local_settings.py, changing `FILENAME_TEMPLATE` to:
8381

8482
You should now get all of a dag log output in a single file.
8583

86-
{% include google_in_article.html %}
87-
8884
## Tailing the logs
8985

9086
Start the scheduler and trigger a dag.

docs/_posts/jsonrpc/2016-08-01-node.markdown

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,8 +53,6 @@ Start the server:
5353
$ node server.js
5454
```
5555

56-
{% include google_in_article.html %}
57-
5856
## Client
5957

6058
Use curl to send requests:

docs/_posts/jsonrpc/2021-08-19-fastapi.markdown

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,8 +55,6 @@ INFO: Application startup complete.
5555
INFO: Uvicorn running on http://127.0.0.1:5000 (Press CTRL+C to quit)
5656
```
5757

58-
{% include google_in_article.html %}
59-
6058
## Test it
6159

6260
Use curl to send a request:

docs/_posts/python/2021-01-27-imports.markdown

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,10 +33,8 @@ import os
3333

3434
## "Related third party imports"
3535

36-
"Third party"
37-
confuses a lot of people. These imports could be maintained by yourself or
38-
your organisation, but are _installed as a
39-
separate package_.
36+
"Third party" confuses a lot of people. These imports could be maintained by
37+
yourself or your organisation, but are _installed as a separate package_.
4038

4139
```python
4240
from airflow.utils.helpers import chain

docs/_posts/python/2021-07-01-code-quality-github-actions.markdown

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,6 @@ I use the following code quality checks:
2222
The following Github Actions workflow will check your code when a Pull
2323
Request is created, catching problems before they're merged.
2424

25-
{% include google_in_article.html %}
26-
2725
## How to add the Github Actions workflow
2826

2927
Add the following to your repository in `.github/workflows/code-quality.yml`.

docs/_posts/python/2021-07-01-code-quality-pre-commit.markdown

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,6 @@ I use the following code quality checks:
2929
These Pre-commit hooks will check your code when you try to commit, catching problems
3030
before they reach your repository.
3131

32-
{% include google_in_article.html %}
33-
3432
## Install the Pre-commit hooks
3533

3634
Add the following `.pre-commit-config.yaml` file to the root of your

0 commit comments

Comments
 (0)