Clarification on MD and AM linter rules.

@bbringhu Here are the current default configuration entries for both the built-in Markdown Lint (MDXXXX) and the Adobe-specific lint (AMXXX) rules.
Here are the current default configuration settings for all Markdown linter rules:
 "markdownlint.config": {
    "line-length": false,
    "AM001": false,
    "AM009": false,
    "AM011": false,
    "MD003": {
      "style": "atx"
    },
    "MD007": {
      "indent": 4
    },
    "MD009": false,
    "MD012": false,
    "MD014": false,
    "MD024": false,
    "MD025": {
      "front_matter_title": ""
    },
    "MD026": false,
    "MD027": false,
    "MD028": false,
    "MD030": {
      "ul_multi": 3,
      "ol_multi": 2
    },
    "MD033": {
      "allowed_elements": [
        "a",
        "b",
        "br",
        "caption",
        "code",
        "col",
        "colgroup",
        "div",
        "em",
        "I",
        "img",
        "li",
        "ol",
        "p",
        "pre",
        "s",
        "span",
        "strong",
        "sub",
        "sup",
        "table",
        "tbody",
        "td",
        "tfoot",
        "th",
        "thead",
        "tr",
        "u",
        "ul"
      ]
    },
    "MD036": false,
    "MD038": false,
    "MD039": false,
    "MD040": false,
    "MD045": false
  },

Here are the descriptions of all of the rules:
Rules
This document contains a description of all rules, what they are checking for,
as well as an examples of documents that break the rule and corrected
versions of the examples.

AM001 - Headings cannot contain numbers without named anchor {#..}
DITA does not allow heading anchors to start with a number

AM002 - ID Tags ({#id-tag-name} cannot contain spaces
DITA does not allow anchor tags to contain spaces

AM003 - Horizontal rules are not supported
DITA does not support horizontal rules

AM004 - Malformed markdown table row
Check for missing close pipes or extra pipes in table

AM005 - Anchor ids {#..} must begin with letter
Similar to AM001, but id must start with letter

AM006 - Detects invisible dodgy-characters and control characters
Checks for hard to find "dodgy" characters that are in the range 0x0 - 0xF.  These are usually the result of cut-and-paste.

AM007 - Heading anchor has no hash
Provide warning about an anchor without a has, such as {anchorid} instead of {#anchorid}

AM008 - Heading contains link
DITA transformation does not support having a link in a heading.

AM009 - Space between blockquote bracket and AFM control
> [!NOTE]

should be
>[!NOTE]

AM010 - ID Tags ({#id-tag-name} cannot contain additional hash symbols
Not allowed: {#id-tag-#name}

MD001 - Heading levels should only increment by one level at a time
Tags: headings, headers
Aliases: heading-increment, header-increment
This rule is triggered when you skip heading levels in a markdown document, for
example:
# Heading 1

### Heading 3

We skipped out a 2nd level heading in this document

When using multiple heading levels, nested headings should increase by only one
level at a time:
# Heading 1

## Heading 2

### Heading 3

#### Heading 4

## Another Heading 2

### Another Heading 3

MD002 - First heading should be a top level heading
Tags: headings, headers
Aliases: first-heading-h1, first-header-h1
Parameters: level (number; default 1)
This rule is triggered when the first heading in the document isn't a h1 heading:
## This isn't a H1 heading

### Another heading

The first heading in the document should be a h1 heading:
# Start with a H1 heading

## Then use a H2 for subsections

Note: The level parameter can be used to change the top level (ex: to h2) in
cases where an h1 is added externally.

MD003 - Heading style
Tags: headings, headers
Aliases: heading-style, header-style
Parameters: style ("consistent", "atx", "atx_closed", "setext",
"setext_with_atx", "setext_with_atx_closed"; default "consistent")
This rule is triggered when different heading styles (atx, setext, and 'closed'
atx) are used in the same document:
# ATX style H1

## Closed ATX style H2 ##

Setext style H1
===============

Be consistent with the style of heading used in a document:
# ATX style H1

## ATX style H2

The setext_with_atx and setext_with_atx_closed doc styles allow atx-style
headings of level 3 or more in documents with setext style headings:
Setext style H1
===============

Setext style H2
---------------

### ATX style H3

Note: the configured heading style can be a specific style to use (atx,
atx_closed, setext, setext_with_atx, setext_with_atx_closed), or simply require
that the usage be consistent within the document.

MD004 - Unordered list style
Tags: bullet, ul
Aliases: ul-style
Parameters: style ("consistent", "asterisk", "plus", "dash", "sublist"; default
"consistent")
This rule is triggered when the symbols used in the document for unordered
list items do not match the configured unordered list style:
* Item 1
+ Item 2
- Item 3

To fix this issue, use the configured style for list items throughout the
document:
* Item 1
* Item 2
* Item 3

The configured list style can be a specific symbol to use (asterisk, plus, dash),
can require that usage be consistent within the document, or can require that each
sublist have a consistent symbol that is different from its parent list.
For example, the following is valid for the sublist style because the outer-most
indent uses asterisk, the middle indent uses plus, and the inner-most indent uses dash:
* Item 1
  + Item 2
    - Item 3
  + Item 4
* Item 4
  + Item 5

MD005 - Inconsistent indentation for list items at the same level
Tags: bullet, ul, indentation
Aliases: list-indent
This rule is triggered when list items are parsed as being at the same level,
but don't have the same indentation:
* Item 1
  * Nested Item 1
  * Nested Item 2
   * A misaligned item

Usually this rule will be triggered because of a typo. Correct the indentation
for the list to fix it:
* Item 1
  * Nested Item 1
  * Nested Item 2
  * Nested Item 3

Sequentially-ordered list markers are usually left-aligned such that all items
have the same starting column:
...
8. Item
9. Item
10. Item
11. Item
...

This rule also supports right-alignment of list markers such that all items have
the same ending column:
...
 8. Item
 9. Item
10. Item
11. Item
...

MD006 - Consider starting bulleted lists at the beginning of the line
Tags: bullet, ul, indentation
Aliases: ul-start-left
This rule is triggered when top level lists don't start at the beginning of a
line:
Some text

  * List item
  * List item

To fix, ensure that top level list items are not indented:
Some test

* List item
* List item

Rationale: Starting lists at the beginning of the line means that nested list
items can all be indented by the same amount when an editor's indent function
or the tab key is used to indent. Starting a list 1 space in means that the
indent of the first nested list is less than the indent of the second level (3
characters if you use 4 space tabs, or 1 character if you use 2 space tabs).
Note: This rule is triggered for the following scenario because the unordered
sublist is not recognized as such by the parser. Not being nested 3 characters
as required by the outer ordered list, it creates a top-level unordered list
instead.
1. List item
  - List item
  - List item
1. List item

MD007 - Unordered list indentation
Tags: bullet, ul, indentation
Aliases: ul-indent
Parameters: indent (number; default 2)
This rule is triggered when list items are not indented by the configured
number of spaces (default: 2).
Example:
* List item
   * Nested list item indented by 3 spaces

Corrected Example:
* List item
  * Nested list item indented by 2 spaces

Rationale (2 space indent): indenting by 2 spaces allows the content of a
nested list to be in line with the start of the content of the parent list
when a single space is used after the list marker.
Rationale (4 space indent): Same indent as code blocks, simpler for editors to
implement. See
http://www.cirosantilli.com/markdown-styleguide/#indented-lists for more
information.
In addition, this is a compatibility issue with multi-markdown parsers, which
require a 4 space indents. See
http://support.markedapp.com/discussions/problems/21-sub-lists-not-indenting
for a description of the problem.
Note: This rule applies to a sublist only if its parent lists are all also
unordered (otherwise, extra indentation of ordered lists interferes with the
rule).

MD009 - Trailing spaces
Tags: whitespace
Aliases: no-trailing-spaces
Parameters: br_spaces, list_item_empty_lines (number; default 2, boolean; default false)
This rule is triggered on any lines that end with unexpected whitespace. To fix this,
remove the trailing space from the end of the line.
The br_spaces parameter allows an exception to this rule for a specific number
of trailing spaces, typically used to insert an explicit line break. The default
value allows 2 spaces to indicate a hard break (<br> element).
Note: You must set br_spaces to a value >= 2 for this parameter to take effect.
Setting br_spaces to 1 behaves the same as 0, disallowing any trailing spaces.
Using spaces to indent blank lines inside a list item is usually not necessary,
but some parsers require it. Set the list_item_empty_lines parameter to true
to allow this:
- list item text
  [2 spaces]
  list item text

MD010 - Hard tabs
Tags: whitespace, hard_tab
Aliases: no-hard-tabs
Parameters: code_blocks (boolean; default true)
This rule is triggered by any lines that contain hard tab characters instead
of using spaces for indentation. To fix this, replace any hard tab characters
with spaces instead.
Example:
Some text

    * hard tab character used to indent the list item

Corrected example:
Some text

    * Spaces used to indent the list item instead

You have the option to exclude this rule for code blocks. To do so, set the
code_blocks parameter to false. Code blocks are included by default since
handling of tabs by tools is often inconsistent (ex: using 4 vs. 8 spaces).

MD011 - Reversed link syntax
Tags: links
Aliases: no-reversed-links
This rule is triggered when text that appears to be a link is encountered, but
where the syntax appears to have been reversed (the [] and () are
reversed):
(Incorrect link syntax)[http://www.example.com/]

To fix this, swap the [] and () around:
[Correct link syntax](http://www.example.com/)

Note: Markdown Extra-style footnotes do not trigger this rule:
For (example)[^1]

MD012 - Multiple consecutive blank lines
Tags: whitespace, blank_lines
Aliases: no-multiple-blanks
Parameters: maximum (number; default 1)
This rule is triggered when there are multiple consecutive blank lines in the
document:
Some text here

Some more text here

To fix this, delete the offending lines:
Some text here

Some more text here

Note: this rule will not be triggered if there are multiple consecutive blank
lines inside code blocks.
Note: The maximum parameter can be used to configure the maximum number of
consecutive blank lines.

MD013 - Line length
Tags: line_length
Aliases: line-length
Parameters: line_length, code_blocks, tables, headings, headers (number; default 80, boolean; default true)

If headings is not provided, headers (deprecated) will be used.

This rule is triggered when there are lines that are longer than the
configured line length (default: 80 characters). To fix this, split the line
up into multiple lines.
This rule has an exception where there is no whitespace beyond the configured
line length. This allows you to still include items such as long URLs without
being forced to break them in the middle.
You have the option to exclude this rule for code blocks, tables, or headings.
To do so, set the code_blocks, tables, or headings parameter(s) to false.
Code blocks are included in this rule by default since it is often a
requirement for document readability, and tentatively compatible with code
rules. Still, some languages do not lend themselves to short lines.

MD014 - Dollar signs used before commands without showing output
Tags: code
Aliases: commands-show-output
This rule is triggered when there are code blocks showing shell commands to be
typed, and the shell commands are preceded by dollar signs ($):
$ ls
$ cat foo
$ less bar

The dollar signs are unnecessary in the above situation, and should not be
included:
ls
cat foo
less bar

However, an exception is made when there is a need to distinguish between
typed commands and command output, as in the following example:
$ ls
foo bar
$ cat foo
Hello world
$ cat bar
baz

Rationale: it is easier to copy and paste and less noisy if the dollar signs
are omitted when they are not needed. See
http://www.cirosantilli.com/markdown-styleguide/#dollar-signs-in-shell-code
for more information.

MD018 - No space after hash on atx style heading
Tags: headings, headers, atx, spaces
Aliases: no-missing-space-atx
This rule is triggered when spaces are missing after the hash characters
in an atx style heading:
#Heading 1

##Heading 2

To fix this, separate the heading text from the hash character by a single
space:
# Heading 1

## Heading 2

MD019 - Multiple spaces after hash on atx style heading
Tags: headings, headers, atx, spaces
Aliases: no-multiple-space-atx
This rule is triggered when more than one space is used to separate the
heading text from the hash characters in an atx style heading:
#  Heading 1

##  Heading 2

To fix this, separate the heading text from the hash character by a single
space:
# Heading 1

## Heading 2

MD020 - No space inside hashes on closed atx style heading
Tags: headings, headers, atx_closed, spaces
Aliases: no-missing-space-closed-atx
This rule is triggered when spaces are missing inside the hash characters
in a closed atx style heading:
#Heading 1#

##Heading 2##

To fix this, separate the heading text from the hash character by a single
space:
# Heading 1 #

## Heading 2 ##

Note: this rule will fire if either side of the heading is missing spaces.

MD021 - Multiple spaces inside hashes on closed atx style heading
Tags: headings, headers, atx_closed, spaces
Aliases: no-multiple-space-closed-atx
This rule is triggered when more than one space is used to separate the
heading text from the hash characters in a closed atx style heading:
#  Heading 1  #

##  Heading 2  ##

To fix this, separate the heading text from the hash character by a single
space:
# Heading 1 #

## Heading 2 ##

Note: this rule will fire if either side of the heading contains multiple
spaces.

MD022 - Headings should be surrounded by blank lines
Tags: headings, headers, blank_lines
Aliases: blanks-around-headings, blanks-around-headers
This rule is triggered when headings (any style) are either not preceded or not
followed by a blank line:
# Heading 1
Some text

Some more text
## Heading 2

To fix this, ensure that all headings have a blank line both before and after
(except where the heading is at the beginning or end of the document):
# Heading 1

Some text

Some more text

## Heading 2

Rationale: Aside from aesthetic reasons, some parsers, including kramdown, will
not parse headings that don't have a blank line before, and will parse them as
regular text.

MD023 - Headings must start at the beginning of the line
Tags: headings, headers, spaces
Aliases: heading-start-left, header-start-left
This rule is triggered when a heading is indented by one or more spaces:
Some text

  # Indented heading

To fix this, ensure that all headings start at the beginning of the line:
Some text

# Heading

Rationale: Headings that don't start at the beginning of the line will not be
parsed as headings, and will instead appear as regular text.

MD024 - Multiple headings with the same content
Tags: headings, headers
Aliases: no-duplicate-heading, no-duplicate-header
Parameters: siblings_only, allow_different_nesting (boolean; default false)
This rule is triggered if there are multiple headings in the document that have
the same text:
# Some text

## Some text

To fix this, ensure that the content of each heading is different:
# Some text

## Some more text

Rationale: Some markdown parses generate anchors for headings based on the
heading name, and having headings with the same content can cause problems with
this.
If the parameter siblings_only (alternatively allow_different_nesting) is
set to true, heading duplication is allowed for non-sibling headings (common
in change logs):
# Change log

## 1.0.0

### Features

## 2.0.0

### Features

MD025 - Multiple top level headings in the same document
Tags: headings, headers
Aliases: single-h1
Parameters: level (number; default 1)
This rule is triggered when a top level heading is in use (the first line of
the file is a h1 heading), and more than one h1 heading is in use in the
document:
# Top level heading

# Another top level heading

To fix, structure your document so that there is a single h1 heading that is
the title for the document, and all later headings are h2 or lower level
headings:
# Title

## Heading

## Another heading

Rationale: A top level heading is a h1 on the first line of the file, and
serves as the title for the document. If this convention is in use, then there
can not be more than one title for the document, and the entire document
should be contained within this heading.
Note: The level parameter can be used to change the top level (ex: to h2) in
cases where an h1 is added externally.

MD026 - Trailing punctuation in heading
Tags: headings, headers
Aliases: no-trailing-punctuation
Parameters: punctuation (string; default ".,;:!?")
This rule is triggered on any heading that has a punctuation character as the
last character in the line:
# This is a heading.

To fix this, remove any trailing punctuation:
# This is a heading

Note: The punctuation parameter can be used to specify what characters class
as punctuation at the end of the heading. For example, you can set it to
".,;:!" to allow headings with question marks in them, such as might be used
in an FAQ.

MD027 - Multiple spaces after blockquote symbol
Tags: blockquote, whitespace, indentation
Aliases: no-multiple-space-blockquote
This rule is triggered when blockquotes have more than one space after the
blockquote (>) symbol:
>  This is a block quote with bad indentation
>  there should only be one.

To fix, remove any extraneous space:
> This is a blockquote with correct
> indentation.

MD028 - Blank line inside blockquote
Tags: blockquote, whitespace
Aliases: no-blanks-blockquote
This rule is triggered when two blockquote blocks are separated by nothing
except for a blank line:
> This is a blockquote
> which is immediately followed by

> this blockquote. Unfortunately
> In some parsers, these are treated as the same blockquote.

To fix this, ensure that any blockquotes that are right next to each other
have some text in between:
> This is a blockquote.

And Jimmy also said:

> This too is a blockquote.

Alternatively, if they are supposed to be the same quote, then add the
blockquote symbol at the beginning of the blank line:
> This is a blockquote.
>
> This is the same blockquote.

Rationale: Some markdown parsers will treat two blockquotes separated by one
or more blank lines as the same blockquote, while others will treat them as
separate blockquotes.

MD029 - Ordered list item prefix
Tags: ol
Aliases: ol-prefix
Parameters: style ("one", "ordered", "one_or_ordered"; default "one_or_ordered")
This rule is triggered on ordered lists that do not either start with '1.' or
do not have a prefix that increases in numerical order (depending on the
configured style).
Example valid list if the style is configured as 'one':
1. Do this.
1. Do that.
1. Done.

Example valid list if the style is configured as 'ordered':
1. Do this.
2. Do that.
3. Done.

Both examples are valid when the style is configured as 'one_or_ordered'.
Example invalid list for all styles:
1. Do this.
3. Done.

This rule supports 0-prefixing ordered list items for uniform indentation:
...
08. Item
09. Item
10. Item
11. Item
...

MD030 - Spaces after list markers
Tags: ol, ul, whitespace
Aliases: list-marker-space
Parameters: ul_single, ol_single, ul_multi, ol_multi (number; default 1)
This rule checks for the number of spaces between a list marker (e.g. '-',
'*', '+' or '1.') and the text of the list item.
The number of spaces checked for depends on the document style in use, but the
default is 1 space after any list marker:
* Foo
* Bar
* Baz

1. Foo
1. Bar
1. Baz

1. Foo
   * Bar
1. Baz

A document style may change the number of spaces after unordered list items
and ordered list items independently, as well as based on whether the content
of every item in the list consists of a single paragraph, or multiple
paragraphs (including sub-lists and code blocks).
For example, the style guide at
http://www.cirosantilli.com/markdown-styleguide/#spaces-after-marker
specifies that 1 space after the list marker should be used if every item in
the list fits within a single paragraph, but to use 2 or 3 spaces (for ordered
and unordered lists respectively) if there are multiple paragraphs of content
inside the list:
* Foo
* Bar
* Baz

vs.
*   Foo

    Second paragraph

*   Bar

or
1.  Foo

    Second paragraph

1.  Bar

To fix this, ensure the correct number of spaces are used after list marker
for your selected document style.

MD031 - Fenced code blocks should be surrounded by blank lines
Tags: code, blank_lines
Aliases: blanks-around-fences
This rule is triggered when fenced code blocks are either not preceded or not
followed by a blank line:
Some text
```
Code block
```

```
Another code block
```
Some more text

To fix this, ensure that all fenced code blocks have a blank line both before
and after (except where the block is at the beginning or end of the document):
Some text

```
Code block
```

```
Another code block
```

Some more text

Rationale: Aside from aesthetic reasons, some parsers, including kramdown, will
not parse fenced code blocks that don't have blank lines before and after them.

MD032 - Lists should be surrounded by blank lines
Tags: bullet, ul, ol, blank_lines
Aliases: blanks-around-lists
This rule is triggered when lists (of any kind) are either not preceded or not
followed by a blank line:
Some text
* Some
* List

1. Some
2. List
Some text

To fix this, ensure that all lists have a blank line both before and after
(except where the block is at the beginning or end of the document):
Some text

* Some
* List

1. Some
2. List

Some text

Rationale: Aside from aesthetic reasons, some parsers, including kramdown, will
not parse lists that don't have blank lines before and after them.
Note: List items without hanging indents are a violation of this rule; list
items with hanging indents are okay:
* This is
not okay

* This is
  okay

MD033 - Inline HTML
Tags: html
Aliases: no-inline-html
Parameters: allowed_elements (array of string; default empty)
This rule is triggered whenever raw HTML is used in a markdown document:
<h1>Inline HTML heading</h1>

To fix this, use 'pure' markdown instead of including raw HTML:
# Markdown heading

Rationale: Raw HTML is allowed in markdown, but this rule is included for
those who want their documents to only include "pure" markdown, or for those
who are rendering markdown documents in something other than HTML.
Note: To allow specific HTML elements, use the 'allowed_elements' parameter.

MD034 - Bare URL used
Tags: links, url
Aliases: no-bare-urls
This rule is triggered whenever a URL is given that isn't surrounded by angle
brackets:
For more information, see http://www.example.com/.

To fix this, add angle brackets around the URL:
For more information, see <http://www.example.com/>.

Rationale: Without angle brackets, the URL isn't converted into a link in many
markdown parsers.
Note: if you do want a bare URL without it being converted into a link,
enclose it in a code block, otherwise in some markdown parsers it will be
converted:
`http://www.example.com`

MD035 - Horizontal rule style
Tags: hr
Aliases: hr-style
Parameters: style ("consistent", "---", "***", or other string specifying the
horizontal rule; default "consistent")
This rule is triggered when inconsistent styles of horizontal rules are used
in the document:
---

- - -

***

* * *

****

To fix this, ensure any horizontal rules used in the document are consistent,
or match the given style if the rule is so configured:
---

---

Note: by default, this rule is configured to just require that all horizontal
rules in the document are the same, and will trigger if any of the horizontal
rules are different than the first one encountered in the document. If you
want to configure the rule to match a specific style, the parameter given to
the 'style' option is a string containing the exact horizontal rule text that
is allowed.

MD036 - Emphasis used instead of a heading
Tags: headings, headers, emphasis
Aliases: no-emphasis-as-heading, no-emphasis-as-header
Parameters: punctuation (string; default ".,;:!?")
This check looks for instances where emphasized (i.e. bold or italic) text is
used to separate sections, where a heading should be used instead:
**My document**

Lorem ipsum dolor sit amet...

_Another section_

Consectetur adipiscing elit, sed do eiusmod.

To fix this, use markdown headings instead of emphasized text to denote
sections:
# My document

Lorem ipsum dolor sit amet...

## Another section

Consectetur adipiscing elit, sed do eiusmod.

Note: this rule looks for single line paragraphs that consist entirely of
emphasized text.  It won't fire on emphasis used within regular text,
multi-line emphasized paragraphs, and paragraphs ending in punctuation.
Similarly to rule MD026, you can configure what characters are recognized as
punctuation.

MD037 - Spaces inside emphasis markers
Tags: whitespace, emphasis
Aliases: no-space-in-emphasis
This rule is triggered when emphasis markers (bold, italic) are used, but they
have spaces between the markers and the text:
Here is some ** bold ** text.

Here is some * italic * text.

Here is some more __ bold __ text.

Here is some more _ italic _ text.

To fix this, remove the spaces around the emphasis markers:
Here is some **bold** text.

Here is some *italic* text.

Here is some more __bold__ text.

Here is some more _italic_ text.

Rationale: Emphasis is only parsed as such when the asterisks/underscores
aren't completely surrounded by spaces. This rule attempts to detect where
they were surrounded by spaces, but it appears that emphasized text was
intended by the author.

MD038 - Spaces inside code span elements
Tags: whitespace, code
Aliases: no-space-in-code
This rule is triggered on code span elements that have spaces right inside the
backticks:
` some text `

`some text `

` some text`

To fix this, remove the spaces inside the codespan markers:
`some text`

Note: A single leading or trailing space is allowed if used to separate codespan
markers from an embedded backtick:
`` ` embedded backtick``

MD039 - Spaces inside link text
Tags: whitespace, links
Aliases: no-space-in-links
This rule is triggered on links that have spaces surrounding the link text:
[ a link ](http://www.example.com/)

To fix this, remove the spaces surrounding the link text:
[a link](http://www.example.com/)

MD040 - Fenced code blocks should have a language specified
Tags: code, language
Aliases: fenced-code-language
This rule is triggered when fenced code blocks are used, but a language isn't
specified:
```
#!/bin/bash
echo Hello world
```

To fix this, add a language specifier to the code block:
```bash
#!/bin/bash
echo Hello world
```

MD041 - First line in file should be a top level heading
Tags: headings, headers
Aliases: first-line-h1
Parameters: level, front_matter_title (number; default 1, string; default "^\s*title:")
This rule is triggered when the first line in the file isn't a top level (h1)
heading:
This is a file without a heading

To fix this, add a heading to the top of your file:
# File with heading

This is a file with a top level heading

The level parameter can be used to change the top level (ex: to h2) in cases
where an h1 is added externally.
If front matter is present and contains a YAML
title property (commonly used with blog posts), this rule will not report a
violation. To use a different property name in front matter, specify the text
of a regular expression via the front_matter_title parameter. To disable the
use of front matter by this rule, specify "" for front_matter_title.

MD042 - No empty links
Tags: links
Aliases: no-empty-links
This rule is triggered when an empty link is encountered:
[an empty link]()

To fix the violation, provide a destination for the link:
[a valid link](https://example.com/)

Empty fragments will trigger this rule:
[an empty fragment](#)

But non-empty fragments will not:
[a valid fragment](#fragment)

MD043 - Required heading structure
Tags: headings, headers
Aliases: required-headings, required-headers
Parameters: headings, headers (array of string; default null for disabled)

If headings is not provided, headers (deprecated) will be used.

This rule is triggered when the headings in a file do not match the array of
headings passed to the rule. It can be used to enforce a standard heading
structure for a set of files.
To require exactly the following structure:
# Head
## Item
### Detail

Set the headings parameter to:
[
    "# Head",
    "## Item",
    "### Detail"
]

To allow optional headings as with the following structure:
# Head
## Item
### Detail (optional)
## Foot
### Notes (optional)

Use the special value "*" meaning "one or more unspecified headings" and set
the headings parameter to:
[
    "# Head",
    "## Item",
    "*",
    "## Foot",
    "*"
]

When an error is detected, this rule outputs the line number of the first
problematic heading (otherwise, it outputs the last line number of the file).
Note that while the headings parameter uses the "## Text" ATX heading style for
simplicity, a file may use any supported heading style.

MD044 - Proper names should have the correct capitalization
Tags: spelling
Aliases: proper-names
Parameters: names, code_blocks (string array; default null, boolean; default true)
This rule is triggered when any of the strings in the names array do not have
the specified capitalization. It can be used to enforce a standard letter case
for the names of projects and products.
For example, the language "JavaScript" is usually written with both the 'J' and
'S' capitalized - though sometimes the 's' or 'j' appear in lower-case. To enforce
the proper capitalization, specify the desired letter case in the names array:
[
    "JavaScript"
]

Set the code_blocks parameter to false to disable this rule for code blocks.

MD045 - Images should have alternate text (alt text)
Tags: accessibility, images
Aliases: no-alt-text
This rule is triggered when an image is missing alternate text (alt text) information.
Alternate text is important for accessibility, describing the content of an image for
people who may not be able to see it.
Alternate text is commonly specified inline as:
![Alternate text](image.jpg)

Or with reference syntax as:
![Alternate text][ref]

...

[ref]: image.jpg "Optional title"

Guidance for writing alternate text is available from the W3C,
Wikipedia, and
other locations.

@geverit4 - Let's resolve this issue with https://github.com/AdobeDocs/adobe-markdown-authoring/issues/26.

Closing because incorporated into #26


Node v88

Is there any timeline for v88 builds? Thanks!

The short answer is no, sorry. If you want to help, the discussions are happening here : #241


Plan for update or official c++ SDK for DocumentDB

Hi,
Is there any plan to develop and update this package or official c++ sdk?
We are looking for a C++ library for DocumentDb and it seems there is no real alternative.
Maybe do you know and other option?
Thank you.

Currently, there is no plan to update this package further. However, I just might find spare time to add new things you might request. I am not aware of any other option. That being said, you are free to take this wrapper and improve on top of it, if that's option for you!


Re disabled attributes

I don't understand why you closed to issue...  But the fix would be to change the code so:
scope.$watch(function () {
                        return attrs.disabled;
                    }, function (newVal) {
                        scope.disabled = newVal;
                    });

You can test at http://amitava82.github.io/angular-multiselect/ and add a disabled attribute to one of the select boxes there and see that it does not work currently.

Works for me http://plnkr.co/edit/csrzsXv18E6GTuXCQpzO?p=preview


Botfront not stable after installation

My name is Joshy Pallan, From India. Currently working in Kuwait. IT Engineer.
First Of All, thanks a lot for you and your team, to make BotFront as an OpenSource Project.
I am working for an Non Profitable Organization, in INDIA,   as requested by the organization, i am in the process of implementing a simple ChatBot,
And i choose BotFront On Premise Product.
i have installed BotFront in a  VM.  Installation went smoothly.  and i have created a simple Chatbot flow using the Web GUI.  it was working fine.  And after 2 days , when i try to login as a admin, it is asking for creating new user.  my previous created setup all vanished...
Could you please help me on this issue.
we are not in a position to go with paid solution.
Thanks in Advance,
Joshy

Hi @joshypallan this is probably related to the volume for MongoDB not set correctly. The data is not persisted outside the container and disappears when the container is restarted. Make sure that the paths in the docker-compose file exist

Dear Nathan,
Thanks for you response,
here below is the content of docker-compose.yml

######################################################################################################
This file is generated when botfront up is invoked.
Changes in .botfront/botfront.yml and .botfront/docker-compose-template.yml will be reflected here
######################################################################################################
version: '3.0'
services:
botfront:
image: 'botfront/botfront:v0.25.9'
container_name: botfront-app
restart: always
networks:
- botfront-network
volumes:
- './models/:/app/models'
ports:
- '8888:3000'
depends_on:
- mongo
env_file:
- .env
environment:
PORT: 3000
botfront-api:
image: 'botfront/botfront-api:v0.25.9'
container_name: botfront-api
networks:
- botfront-network
restart: always
depends_on:
- mongo
ports:
- '8080:8080'
env_file:
- .env
rasa:
build:
context: ./rasa
args:
RASA_IMAGE: '${IMAGES_CURRENT_RASA}'
container_name: botfront-rasa
networks:
- botfront-network
restart: always
ports:
- '5005:5005'
volumes:
- './models/:/app/models'
env_file:
- .env
actions:
build:
context: ./actions
args:
RASA_SDK_IMAGE: '${IMAGES_CURRENT_ACTIONS}'
container_name: botfront-actions
networks:
- botfront-network
restart: always
ports:
- '5055:5055'
volumes:
- './actions:/app/actions'
command:
- start
- '--debug'
- '--actions'
- actions
env_file:
- .env
duckling:
image: 'botfront/duckling:latest'
container_name: botfront-duckling
networks:
- botfront-network
restart: always
ports:
- '8000:8000'
mongo:
image: 'mongo:latest'
container_name: botfront-mongo
restart: always
networks:
- botfront-network
volumes:
- './botfront-db:/data/db'
ports:
- '27017:27017'
env_file:
- .env
networks:
botfront-network: {}
volumes:
botfront-db: null
Could you please verify, i am new to BotFront Chatbot.
Thanks in Advance,
Joshy Jose Pallan

The folders botfront-db and models must exist, be accessible, and the user running botfront must have write permissions in them

Did all of  this but still my data is disappearing. Please help


Recipe Added: Check Budget using testspecs

Recipe Added as demanded by Sir 🙂.
Please take a look at perf budges if required we can add more metrices.

Done!


http://phosphorus.github.io/#119796256

No sprites showing.

http://htmlgames.github.io/htmlgames/differences/UAT/itchy/index.html#119796256

Works fine…

Yeah sorry, does now. I was using vector graphics.

From: Nathan<EMAIL_ADDRESS>Sent: 02 September 2016 18:50
To: nathan/phosphorus
Cc: Daniel Harrin; Author
Subject: Re: [nathan/phosphorus] http://phosphorus.github.io/#119796256 (#690)
Works fine...

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/nathan/phosphorus/issues/690#issuecomment-244458318, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALkDHzSgSkdWMwAKY49tya0C6SXGwYWXks5qmG_6gaJpZM4Jz5ov.


Translate docs into Chinese

I am really like the Hanzi Writer project, I am very happy to do this job. I changed the code structure, if some places do not work well, you do it.

Amazing work! Thank you so much for doing this!! I'll test this out a bit more and then try to get it merged in the next day or so! 🎉🎉🎉

Thank you very much. Thank you review code, it is important for me.

Looks great! Thanks so much for doing this!!


Feature : Set plugin search path (esp for MSVC)

Apologies if these types of questions are better referred to a forum.
Where can plugins be located?
(especially on windows)
I'm reading:
    plugin_file_name = squash_strdup_printf ("%s/%ssquash%s-plugin-%s%s", plugin->directory, SQUASH_SHARED_LIBRARY_PREFIX, SQUASH_VERSION_API, plugin->name, SQUASH_SHARED_LIBRARY_SUFFIX);

from plugin.c
And in config.h:
#define SQUASH_INSTALL_PREFIX "C:/Program Files/squash"
#define SQUASH_PLUGIN_DIR "C:/Program Files/squash/lib/squash/0.8/plugins"
#define SQUASH_SEARCH_PATH "C:/Program Files/squash/lib/squash/0.8/plugins"
#define SQUASH_SHARED_LIBRARY_PREFIX ""
#define SQUASH_SHARED_LIBRARY_SUFFIX ".dll"
#define SQUASH_BUILD_TYPE ""

(side question : is this config.h written by c-make?)
I'm finding that the Install script (which halted when it got to density) put the dll's into that SQUASH_PLUGIN_DIR with the correct hierarchy structure. So those plugins appear by default.
Q1) Does squash search for plugins at this location only (i.e. not locally)?
Q2) Can the user specify a search path for plugins?
I can see:
SquashPlugin*
squash_plugin_new (char* name, char* directory, SquashContext* context) {
  SquashPlugin* plugin = (SquashPlugin*) squash_malloc (sizeof (SquashPlugin));

in plugin.c
and
squash_context_add_plugin (SquashContext* context, char* name, char* directory) {

in context.c (which calls squash_plugin_new)
These functions are not exposed in the headers.
Q3) Is there a good way to publicly operate this functions?
I've tried manually copying plugins into this folder:
When I call squash_foreach_codec I get

brieflz
brotli
bsc
bzip2
copy
crush
density (not valid)

These plugins (except density) were copied by the INSTALL project to the Program Files location. However density dll is missing, and if I add another plugin manually:

Then it is not shown in the list.
Q4) Is this plugin list configured somewhere? (rather than searching the directory)
Ideally I want to be able to keep my squash and plugin dll's next to my application
(to make the application portable, but also to make the development environment portable)
Ideally something like this:

(or perhaps in a subdir plugins/squash)
Thank you

Apologies if these types of questions are better referred to a forum.

That's probably a good idea.  See http://quixdb.github.io/squash/#support.  The mailing list (which doubles as a forum) is probably the most appropriate place for this discussion.  The issue tracker is more for, well, issues.  I guess if you phrased it as "Document plugin locations on Windows", which I'll change the title to.

Where can plugins be located?
(especially on windows)

First, a SQUASH_PLUGINS environment variable is checked.  If the variable is set (getenv(SQUASH_PLUGINS) != NULL), that path will be used as the search path.
If the SQUASH_PLUGINS environment variable is not set, it will use the SQUASH_SEARCH_PATH value defined by CMake and written to config.h (which, to be clear, is a private header, and will not be installed).  The default value for this is the same as the directory CMake install the plugins to, which is ${CMAKE_INSTALL_FULL_LIBDIR}/squash/${SQUASH_VERSION_API}/plugins, but you can override it at configure time (cmake -DSEARCH_PATH="whatever").
On Windows the search path is is a semi-colon separated list of directories.  On other operating systems it is a colon-separated list.  Other than that, the only real difference between Windows and other operating systems is that other operating systems have a standard location we can install plugins to, so everything just works.  On Windows you pretty much have to set the search path yourself, either at compile time or run time.
When searching for plugins, Squash will look for $current_search_path/*/squash.ini to detect if a plugin is present.  If so, it will parse the ini, but will not load the DLL.

These functions are not exposed in the headers.
Q3) Is there a good way to publicly operate this functions?

No.  In the future I might consider an API to set the search path, but TBH I don't see a reason not to just use setenv (or, on Windows, putenv_s) to set the SQUASH_PLUGINS environment variable.  I'm not going to say I'll never expose the squash_plugin_new or squash_context_add_plugin, but it would require a very compelling use case that I haven't thought of.

Q4) Is this plugin list configured somewhere? (rather than searching the directory)

Nope, there is no hardcoded list.  You can add and remove plugins at will.  Otherwise it would be impossible for third parties to distribute plugins.  The plugin enumeration code probably bails if it fails to load a plugin; I'll look into fixing that.  Unfortunately, as plugins are loaded on-demand, if a squash.ini exists for a plugin but the DLL doesn't work for any reason (like, say, the DLL being missing) we won't know about it until you actually try to do something with the plugin.

Ideally I want to be able to keep my squash and plugin dll's next to my application
(to make the application portable, but also to make the development environment portable)
Ideally something like this:

The INI files are definitely necessary, so the structure proposed in your screenshot definitely will not work.  The currently supported way to do this would be to create a folder for each plugin, and have the DLL and INI files for the plugin in that folder.  Something like:

data/
assimp.dll
fmodex.dll
…
squash0.8.dll
squash-plugins/
squash-plugins/brieflz/
squash-plugins/brieflz/squash.ini
squash-plugins/brieflz/squash0.8-plugin-brieflz.dll
…

Then use the SQUASH_PLUGINS environment variable to set the search path to $path_to_your_dir/squash
Technically you don't really need the "squash-plugins/" directory; you could set the search path to just $path_to_your_dir, but that seems rather ugly to me.  You could also call it something other than "squash-plugins", but inside of that directory the file structure needs to be pretty strict.

(or perhaps in a subdir plugins/squash)

Yep, plugins/squash would work, too.

I've tried manually copying plugins into this folder:
When I call squash_foreach_codec I get

I don't suppose you could share the source code for this?  When I remove the density shared library here it's handled pretty well here…

From https://social.msdn.microsoft.com/Forums/vstudio/en-US/e115ed93-f9eb-49ba-a1db-b3f4ee02bd93/application-ignores-env-variables-setting?forum=vcgeneral

So if your application then calls putenv then it will actually call putenv in msvcr100.dll not msvcrt.dll. This actually turns out to be a problem because dynamic versions of the CRT don't share data between versions, so while all modules using msvcr100.dll would share data, such as environment variables, these are not shared between the modules using msvcr100.dll and msvcrt.dll.

Since squash is a dll, it uses whichever MSVCR runtime it happened to be built with. So _putenv_s, etc won't work if your application is using a different runtime (e.g. debug runtime). Possible workarounds:

Use a seperate squash dll for debug mode
Have a squash_set_plugin_dir() function  (this sounds the best!)
Have a squash_put_env_var or similar which allows you to set environment variables 'through' the squash dll, to ensure that the environment variables are being set in the right context for squash to listen to them

Here's a hack attempt at this:
https://github.com/elliotwoods/squash/commit/17e210ba6a945d39cfa530c35f59b6cfae577020

Since squash is a dll, it uses whichever MSVCR runtime it happened to be built with. So _putenv_s, etc won't work if your application is using a different runtime (e.g. debug runtime).

That is just awful. I found an article with a deeper explanation here, which suggest providing your own wrappers for getenv() and putenv() to work around this issue.
Back when we were using glib for testing we had an issue with crashes on Windows when closing file handles, which was the same issue.

Okay, this should be sorted now, thanks for the help.  I had no idea Windows would mix runtimes in a single executable.

Here's a hack attempt at this:
elliotwoods@17e210b

Thanks :).  I ended up doing something pretty similar.
I didn't like the idea of overriding the SQUASH_PLUGINS environment variable; I think SQUASH_PLUGINS should have priority, so my patch adds another layer in between the compile-time default and the environment variable.

That is just awful.

Agreed.

I found an article with a deeper explanation here, which suggest providing your own wrappers for getenv() and putenv() to work around this issue.

Thanks for that; interesting (/horrifying) reading.  I guess we should add some warnings to the squash_file_steal and squash_file_free functions…

thank you! i'll move over to the new code right away


MaMuT-like feature requests.

Behaviour to implement.

[x] Jump between cell divisions with “v" (forward) and “b" (backwards) - in already traced cell lineages.
[x] Selection behaviours to select

[x] a whole track
[x] track upward in time
[x] track downward in time
from a selection.

Action framework.

[ ] Generate missing spots across a gap over several frames by interpolating new spot positions.
[ ] Automatic cell naming within tracks. To complete this one, we require a documented naming scheme.

Feature framework.

[x] Maintain a set of manual labels (10 or so) for each spot. Should be manually editable, ideally a bit like an enum type (you can have 1000 cells but their 'state' label has only 5 values).
[ ] Generate spot colouring from feature.
[x] Store, make editable and display a manual color for spots.

The remainder of this issue will be managed in a github project.


Writing CutoffTime to clients/content/lib/google_api/content/v21/model/cutoff_time.ex.
Writing Datafeed to clients/content/lib/google_api/content/v21/model/datafeed.ex.
Writing DatafeedFetchSchedule to clients/content/lib/google_api/content/v21/model/datafeed_fetch_schedule.ex.
Writing DatafeedFormat to clients/content/lib/google_api/content/v21/model/datafeed_format.ex.
Writing DatafeedStatus to clients/content/lib/google_api/content/v21/model/datafeed_status.ex.
Writing DatafeedStatusError to clients/content/lib/google_api/content/v21/model/datafeed_status_error.ex.
Writing DatafeedStatusExample to clients/content/lib/google_api/content/v21/model/datafeed_status_example.ex.
Writing DatafeedTarget to clients/content/lib/google_api/content/v21/model/datafeed_target.ex.
Writing DatafeedsCustomBatchRequest to clients/content/lib/google_api/content/v21/model/datafeeds_custom_batch_request.ex.
Writing DatafeedsCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/datafeeds_custom_batch_request_entry.ex.
Writing DatafeedsCustomBatchResponse to clients/content/lib/google_api/content/v21/model/datafeeds_custom_batch_response.ex.
Writing DatafeedsCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/datafeeds_custom_batch_response_entry.ex.
Writing DatafeedsFetchNowResponse to clients/content/lib/google_api/content/v21/model/datafeeds_fetch_now_response.ex.
Writing DatafeedsListResponse to clients/content/lib/google_api/content/v21/model/datafeeds_list_response.ex.
Writing DatafeedstatusesCustomBatchRequest to clients/content/lib/google_api/content/v21/model/datafeedstatuses_custom_batch_request.ex.
Writing DatafeedstatusesCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/datafeedstatuses_custom_batch_request_entry.ex.
Writing DatafeedstatusesCustomBatchResponse to clients/content/lib/google_api/content/v21/model/datafeedstatuses_custom_batch_response.ex.
Writing DatafeedstatusesCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/datafeedstatuses_custom_batch_response_entry.ex.
Writing DatafeedstatusesListResponse to clients/content/lib/google_api/content/v21/model/datafeedstatuses_list_response.ex.
Writing DeliveryTime to clients/content/lib/google_api/content/v21/model/delivery_time.ex.
Writing Error to clients/content/lib/google_api/content/v21/model/error.ex.
Writing Errors to clients/content/lib/google_api/content/v21/model/errors.ex.
Writing GmbAccounts to clients/content/lib/google_api/content/v21/model/gmb_accounts.ex.
Writing GmbAccountsGmbAccount to clients/content/lib/google_api/content/v21/model/gmb_accounts_gmb_account.ex.
Writing Headers to clients/content/lib/google_api/content/v21/model/headers.ex.
Writing HolidayCutoff to clients/content/lib/google_api/content/v21/model/holiday_cutoff.ex.
Writing HolidaysHoliday to clients/content/lib/google_api/content/v21/model/holidays_holiday.ex.
Writing Installment to clients/content/lib/google_api/content/v21/model/installment.ex.
Writing InvoiceSummary to clients/content/lib/google_api/content/v21/model/invoice_summary.ex.
Writing InvoiceSummaryAdditionalChargeSummary to clients/content/lib/google_api/content/v21/model/invoice_summary_additional_charge_summary.ex.
Writing LiaAboutPageSettings to clients/content/lib/google_api/content/v21/model/lia_about_page_settings.ex.
Writing LiaCountrySettings to clients/content/lib/google_api/content/v21/model/lia_country_settings.ex.
Writing LiaInventorySettings to clients/content/lib/google_api/content/v21/model/lia_inventory_settings.ex.
Writing LiaOnDisplayToOrderSettings to clients/content/lib/google_api/content/v21/model/lia_on_display_to_order_settings.ex.
Writing LiaPosDataProvider to clients/content/lib/google_api/content/v21/model/lia_pos_data_provider.ex.
Writing LiaSettings to clients/content/lib/google_api/content/v21/model/lia_settings.ex.
Writing LiasettingsCustomBatchRequest to clients/content/lib/google_api/content/v21/model/liasettings_custom_batch_request.ex.
Writing LiasettingsCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/liasettings_custom_batch_request_entry.ex.
Writing LiasettingsCustomBatchResponse to clients/content/lib/google_api/content/v21/model/liasettings_custom_batch_response.ex.
Writing LiasettingsCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/liasettings_custom_batch_response_entry.ex.
Writing LiasettingsGetAccessibleGmbAccountsResponse to clients/content/lib/google_api/content/v21/model/liasettings_get_accessible_gmb_accounts_response.ex.
Writing LiasettingsListPosDataProvidersResponse to clients/content/lib/google_api/content/v21/model/liasettings_list_pos_data_providers_response.ex.
Writing LiasettingsListResponse to clients/content/lib/google_api/content/v21/model/liasettings_list_response.ex.
Writing LiasettingsRequestGmbAccessResponse to clients/content/lib/google_api/content/v21/model/liasettings_request_gmb_access_response.ex.
Writing LiasettingsRequestInventoryVerificationResponse to clients/content/lib/google_api/content/v21/model/liasettings_request_inventory_verification_response.ex.
Writing LiasettingsSetInventoryVerificationContactResponse to clients/content/lib/google_api/content/v21/model/liasettings_set_inventory_verification_contact_response.ex.
Writing LiasettingsSetPosDataProviderResponse to clients/content/lib/google_api/content/v21/model/liasettings_set_pos_data_provider_response.ex.
Writing LinkService to clients/content/lib/google_api/content/v21/model/link_service.ex.
Writing LinkedAccount to clients/content/lib/google_api/content/v21/model/linked_account.ex.
Writing LocalInventory to clients/content/lib/google_api/content/v21/model/local_inventory.ex.
Writing LocalinventoryCustomBatchRequest to clients/content/lib/google_api/content/v21/model/localinventory_custom_batch_request.ex.
Writing LocalinventoryCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/localinventory_custom_batch_request_entry.ex.
Writing LocalinventoryCustomBatchResponse to clients/content/lib/google_api/content/v21/model/localinventory_custom_batch_response.ex.
Writing LocalinventoryCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/localinventory_custom_batch_response_entry.ex.
Writing LocationIdSet to clients/content/lib/google_api/content/v21/model/location_id_set.ex.
Writing LoyaltyPoints to clients/content/lib/google_api/content/v21/model/loyalty_points.ex.
Writing MerchantOrderReturn to clients/content/lib/google_api/content/v21/model/merchant_order_return.ex.
Writing MerchantOrderReturnItem to clients/content/lib/google_api/content/v21/model/merchant_order_return_item.ex.
Writing MerchantRejectionReason to clients/content/lib/google_api/content/v21/model/merchant_rejection_reason.ex.
Writing MinimumOrderValueTable to clients/content/lib/google_api/content/v21/model/minimum_order_value_table.ex.
Writing MinimumOrderValueTableStoreCodeSetWithMov to clients/content/lib/google_api/content/v21/model/minimum_order_value_table_store_code_set_with_mov.ex.
Writing MonetaryAmount to clients/content/lib/google_api/content/v21/model/monetary_amount.ex.
Writing Order to clients/content/lib/google_api/content/v21/model/order.ex.
Writing OrderAddress to clients/content/lib/google_api/content/v21/model/order_address.ex.
Writing OrderCancellation to clients/content/lib/google_api/content/v21/model/order_cancellation.ex.
Writing OrderCustomer to clients/content/lib/google_api/content/v21/model/order_customer.ex.
Writing OrderCustomerLoyaltyInfo to clients/content/lib/google_api/content/v21/model/order_customer_loyalty_info.ex.
Writing OrderCustomerMarketingRightsInfo to clients/content/lib/google_api/content/v21/model/order_customer_marketing_rights_info.ex.
Writing OrderDeliveryDetails to clients/content/lib/google_api/content/v21/model/order_delivery_details.ex.
Writing OrderLineItem to clients/content/lib/google_api/content/v21/model/order_line_item.ex.
Writing OrderLineItemAdjustment to clients/content/lib/google_api/content/v21/model/order_line_item_adjustment.ex.
Writing OrderLineItemProduct to clients/content/lib/google_api/content/v21/model/order_line_item_product.ex.
Writing OrderLineItemProductFee to clients/content/lib/google_api/content/v21/model/order_line_item_product_fee.ex.
Writing OrderLineItemProductVariantAttribute to clients/content/lib/google_api/content/v21/model/order_line_item_product_variant_attribute.ex.
Writing OrderLineItemReturnInfo to clients/content/lib/google_api/content/v21/model/order_line_item_return_info.ex.
Writing OrderLineItemShippingDetails to clients/content/lib/google_api/content/v21/model/order_line_item_shipping_details.ex.
Writing OrderLineItemShippingDetailsMethod to clients/content/lib/google_api/content/v21/model/order_line_item_shipping_details_method.ex.
Writing OrderMerchantProvidedAnnotation to clients/content/lib/google_api/content/v21/model/order_merchant_provided_annotation.ex.
Writing OrderPickupDetails to clients/content/lib/google_api/content/v21/model/order_pickup_details.ex.
Writing OrderPickupDetailsCollector to clients/content/lib/google_api/content/v21/model/order_pickup_details_collector.ex.
Writing OrderPromotion to clients/content/lib/google_api/content/v21/model/order_promotion.ex.
Writing OrderPromotionItem to clients/content/lib/google_api/content/v21/model/order_promotion_item.ex.
Writing OrderRefund to clients/content/lib/google_api/content/v21/model/order_refund.ex.
Writing OrderReportDisbursement to clients/content/lib/google_api/content/v21/model/order_report_disbursement.ex.
Writing OrderReportTransaction to clients/content/lib/google_api/content/v21/model/order_report_transaction.ex.
Writing OrderReturn to clients/content/lib/google_api/content/v21/model/order_return.ex.
Writing OrderShipment to clients/content/lib/google_api/content/v21/model/order_shipment.ex.
Writing OrderShipmentLineItemShipment to clients/content/lib/google_api/content/v21/model/order_shipment_line_item_shipment.ex.
Writing OrderinvoicesCreateChargeInvoiceRequest to clients/content/lib/google_api/content/v21/model/orderinvoices_create_charge_invoice_request.ex.
Writing OrderinvoicesCreateChargeInvoiceResponse to clients/content/lib/google_api/content/v21/model/orderinvoices_create_charge_invoice_response.ex.
Writing OrderinvoicesCreateRefundInvoiceRequest to clients/content/lib/google_api/content/v21/model/orderinvoices_create_refund_invoice_request.ex.
Writing OrderinvoicesCreateRefundInvoiceResponse to clients/content/lib/google_api/content/v21/model/orderinvoices_create_refund_invoice_response.ex.
Writing OrderinvoicesCustomBatchRequestEntryCreateRefundInvoiceRefundOption to clients/content/lib/google_api/content/v21/model/orderinvoices_custom_batch_request_entry_create_refund_invoice_refund_option.ex.
Writing OrderinvoicesCustomBatchRequestEntryCreateRefundInvoiceReturnOption to clients/content/lib/google_api/content/v21/model/orderinvoices_custom_batch_request_entry_create_refund_invoice_return_option.ex.
Writing OrderreportsListDisbursementsResponse to clients/content/lib/google_api/content/v21/model/orderreports_list_disbursements_response.ex.
Writing OrderreportsListTransactionsResponse to clients/content/lib/google_api/content/v21/model/orderreports_list_transactions_response.ex.
Writing OrderreturnsAcknowledgeRequest to clients/content/lib/google_api/content/v21/model/orderreturns_acknowledge_request.ex.
Writing OrderreturnsAcknowledgeResponse to clients/content/lib/google_api/content/v21/model/orderreturns_acknowledge_response.ex.
Writing OrderreturnsListResponse to clients/content/lib/google_api/content/v21/model/orderreturns_list_response.ex.
Writing OrderreturnsPartialRefund to clients/content/lib/google_api/content/v21/model/orderreturns_partial_refund.ex.
Writing OrderreturnsProcessRequest to clients/content/lib/google_api/content/v21/model/orderreturns_process_request.ex.
Writing OrderreturnsProcessResponse to clients/content/lib/google_api/content/v21/model/orderreturns_process_response.ex.
Writing OrderreturnsRefundOperation to clients/content/lib/google_api/content/v21/model/orderreturns_refund_operation.ex.
Writing OrderreturnsRejectOperation to clients/content/lib/google_api/content/v21/model/orderreturns_reject_operation.ex.
Writing OrderreturnsReturnItem to clients/content/lib/google_api/content/v21/model/orderreturns_return_item.ex.
Writing OrdersAcknowledgeRequest to clients/content/lib/google_api/content/v21/model/orders_acknowledge_request.ex.
Writing OrdersAcknowledgeResponse to clients/content/lib/google_api/content/v21/model/orders_acknowledge_response.ex.
Writing OrdersAdvanceTestOrderResponse to clients/content/lib/google_api/content/v21/model/orders_advance_test_order_response.ex.
Writing OrdersCancelLineItemRequest to clients/content/lib/google_api/content/v21/model/orders_cancel_line_item_request.ex.
Writing OrdersCancelLineItemResponse to clients/content/lib/google_api/content/v21/model/orders_cancel_line_item_response.ex.
Writing OrdersCancelRequest to clients/content/lib/google_api/content/v21/model/orders_cancel_request.ex.
Writing OrdersCancelResponse to clients/content/lib/google_api/content/v21/model/orders_cancel_response.ex.
Writing OrdersCancelTestOrderByCustomerRequest to clients/content/lib/google_api/content/v21/model/orders_cancel_test_order_by_customer_request.ex.
Writing OrdersCancelTestOrderByCustomerResponse to clients/content/lib/google_api/content/v21/model/orders_cancel_test_order_by_customer_response.ex.
Writing OrdersCreateTestOrderRequest to clients/content/lib/google_api/content/v21/model/orders_create_test_order_request.ex.
Writing OrdersCreateTestOrderResponse to clients/content/lib/google_api/content/v21/model/orders_create_test_order_response.ex.
Writing OrdersCreateTestReturnRequest to clients/content/lib/google_api/content/v21/model/orders_create_test_return_request.ex.
Writing OrdersCreateTestReturnResponse to clients/content/lib/google_api/content/v21/model/orders_create_test_return_response.ex.
Writing OrdersCustomBatchRequestEntryCreateTestReturnReturnItem to clients/content/lib/google_api/content/v21/model/orders_custom_batch_request_entry_create_test_return_return_item.ex.
Writing OrdersCustomBatchRequestEntryShipLineItemsShipmentInfo to clients/content/lib/google_api/content/v21/model/orders_custom_batch_request_entry_ship_line_items_shipment_info.ex.
Writing OrdersGetByMerchantOrderIdResponse to clients/content/lib/google_api/content/v21/model/orders_get_by_merchant_order_id_response.ex.
Writing OrdersGetTestOrderTemplateResponse to clients/content/lib/google_api/content/v21/model/orders_get_test_order_template_response.ex.
Writing OrdersInStoreRefundLineItemRequest to clients/content/lib/google_api/content/v21/model/orders_in_store_refund_line_item_request.ex.
Writing OrdersInStoreRefundLineItemResponse to clients/content/lib/google_api/content/v21/model/orders_in_store_refund_line_item_response.ex.
Writing OrdersListResponse to clients/content/lib/google_api/content/v21/model/orders_list_response.ex.
Writing OrdersRejectReturnLineItemRequest to clients/content/lib/google_api/content/v21/model/orders_reject_return_line_item_request.ex.
Writing OrdersRejectReturnLineItemResponse to clients/content/lib/google_api/content/v21/model/orders_reject_return_line_item_response.ex.
Writing OrdersReturnRefundLineItemRequest to clients/content/lib/google_api/content/v21/model/orders_return_refund_line_item_request.ex.
Writing OrdersReturnRefundLineItemResponse to clients/content/lib/google_api/content/v21/model/orders_return_refund_line_item_response.ex.
Writing OrdersSetLineItemMetadataRequest to clients/content/lib/google_api/content/v21/model/orders_set_line_item_metadata_request.ex.
Writing OrdersSetLineItemMetadataResponse to clients/content/lib/google_api/content/v21/model/orders_set_line_item_metadata_response.ex.
Writing OrdersShipLineItemsRequest to clients/content/lib/google_api/content/v21/model/orders_ship_line_items_request.ex.
Writing OrdersShipLineItemsResponse to clients/content/lib/google_api/content/v21/model/orders_ship_line_items_response.ex.
Writing OrdersUpdateLineItemShippingDetailsRequest to clients/content/lib/google_api/content/v21/model/orders_update_line_item_shipping_details_request.ex.
Writing OrdersUpdateLineItemShippingDetailsResponse to clients/content/lib/google_api/content/v21/model/orders_update_line_item_shipping_details_response.ex.
Writing OrdersUpdateMerchantOrderIdRequest to clients/content/lib/google_api/content/v21/model/orders_update_merchant_order_id_request.ex.
Writing OrdersUpdateMerchantOrderIdResponse to clients/content/lib/google_api/content/v21/model/orders_update_merchant_order_id_response.ex.
Writing OrdersUpdateShipmentRequest to clients/content/lib/google_api/content/v21/model/orders_update_shipment_request.ex.
Writing OrdersUpdateShipmentResponse to clients/content/lib/google_api/content/v21/model/orders_update_shipment_response.ex.
Writing PickupCarrierService to clients/content/lib/google_api/content/v21/model/pickup_carrier_service.ex.
Writing PickupServicesPickupService to clients/content/lib/google_api/content/v21/model/pickup_services_pickup_service.ex.
Writing PosCustomBatchRequest to clients/content/lib/google_api/content/v21/model/pos_custom_batch_request.ex.
Writing PosCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/pos_custom_batch_request_entry.ex.
Writing PosCustomBatchResponse to clients/content/lib/google_api/content/v21/model/pos_custom_batch_response.ex.
Writing PosCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/pos_custom_batch_response_entry.ex.
Writing PosDataProviders to clients/content/lib/google_api/content/v21/model/pos_data_providers.ex.
Writing PosDataProvidersPosDataProvider to clients/content/lib/google_api/content/v21/model/pos_data_providers_pos_data_provider.ex.
Writing PosInventory to clients/content/lib/google_api/content/v21/model/pos_inventory.ex.
Writing PosInventoryRequest to clients/content/lib/google_api/content/v21/model/pos_inventory_request.ex.
Writing PosInventoryResponse to clients/content/lib/google_api/content/v21/model/pos_inventory_response.ex.
Writing PosListResponse to clients/content/lib/google_api/content/v21/model/pos_list_response.ex.
Writing PosSale to clients/content/lib/google_api/content/v21/model/pos_sale.ex.
Writing PosSaleRequest to clients/content/lib/google_api/content/v21/model/pos_sale_request.ex.
Writing PosSaleResponse to clients/content/lib/google_api/content/v21/model/pos_sale_response.ex.
Writing PosStore to clients/content/lib/google_api/content/v21/model/pos_store.ex.
Writing PostalCodeGroup to clients/content/lib/google_api/content/v21/model/postal_code_group.ex.
Writing PostalCodeRange to clients/content/lib/google_api/content/v21/model/postal_code_range.ex.
Writing Price to clients/content/lib/google_api/content/v21/model/price.ex.
Writing Product to clients/content/lib/google_api/content/v21/model/product.ex.
Writing ProductAmount to clients/content/lib/google_api/content/v21/model/product_amount.ex.
Writing ProductShipping to clients/content/lib/google_api/content/v21/model/product_shipping.ex.
Writing ProductShippingDimension to clients/content/lib/google_api/content/v21/model/product_shipping_dimension.ex.
Writing ProductShippingWeight to clients/content/lib/google_api/content/v21/model/product_shipping_weight.ex.
Writing ProductStatus to clients/content/lib/google_api/content/v21/model/product_status.ex.
Writing ProductStatusDestinationStatus to clients/content/lib/google_api/content/v21/model/product_status_destination_status.ex.
Writing ProductStatusItemLevelIssue to clients/content/lib/google_api/content/v21/model/product_status_item_level_issue.ex.
Writing ProductTax to clients/content/lib/google_api/content/v21/model/product_tax.ex.
Writing ProductUnitPricingBaseMeasure to clients/content/lib/google_api/content/v21/model/product_unit_pricing_base_measure.ex.
Writing ProductUnitPricingMeasure to clients/content/lib/google_api/content/v21/model/product_unit_pricing_measure.ex.
Writing ProductsCustomBatchRequest to clients/content/lib/google_api/content/v21/model/products_custom_batch_request.ex.
Writing ProductsCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/products_custom_batch_request_entry.ex.
Writing ProductsCustomBatchResponse to clients/content/lib/google_api/content/v21/model/products_custom_batch_response.ex.
Writing ProductsCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/products_custom_batch_response_entry.ex.
Writing ProductsListResponse to clients/content/lib/google_api/content/v21/model/products_list_response.ex.
Writing ProductstatusesCustomBatchRequest to clients/content/lib/google_api/content/v21/model/productstatuses_custom_batch_request.ex.
Writing ProductstatusesCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/productstatuses_custom_batch_request_entry.ex.
Writing ProductstatusesCustomBatchResponse to clients/content/lib/google_api/content/v21/model/productstatuses_custom_batch_response.ex.
Writing ProductstatusesCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/productstatuses_custom_batch_response_entry.ex.
Writing ProductstatusesListResponse to clients/content/lib/google_api/content/v21/model/productstatuses_list_response.ex.
Writing PubsubNotificationSettings to clients/content/lib/google_api/content/v21/model/pubsub_notification_settings.ex.
Writing RateGroup to clients/content/lib/google_api/content/v21/model/rate_group.ex.
Writing RefundReason to clients/content/lib/google_api/content/v21/model/refund_reason.ex.
Writing RegionalInventory to clients/content/lib/google_api/content/v21/model/regional_inventory.ex.
Writing RegionalinventoryCustomBatchRequest to clients/content/lib/google_api/content/v21/model/regionalinventory_custom_batch_request.ex.
Writing RegionalinventoryCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/regionalinventory_custom_batch_request_entry.ex.
Writing RegionalinventoryCustomBatchResponse to clients/content/lib/google_api/content/v21/model/regionalinventory_custom_batch_response.ex.
Writing RegionalinventoryCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/regionalinventory_custom_batch_response_entry.ex.
Writing ReturnAddress to clients/content/lib/google_api/content/v21/model/return_address.ex.
Writing ReturnAddressAddress to clients/content/lib/google_api/content/v21/model/return_address_address.ex.
Writing ReturnPolicy to clients/content/lib/google_api/content/v21/model/return_policy.ex.
Writing ReturnPolicyPolicy to clients/content/lib/google_api/content/v21/model/return_policy_policy.ex.
Writing ReturnPolicySeasonalOverride to clients/content/lib/google_api/content/v21/model/return_policy_seasonal_override.ex.
Writing ReturnPricingInfo to clients/content/lib/google_api/content/v21/model/return_pricing_info.ex.
Writing ReturnShipment to clients/content/lib/google_api/content/v21/model/return_shipment.ex.
Writing ReturnaddressCustomBatchRequest to clients/content/lib/google_api/content/v21/model/returnaddress_custom_batch_request.ex.
Writing ReturnaddressCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/returnaddress_custom_batch_request_entry.ex.
Writing ReturnaddressCustomBatchResponse to clients/content/lib/google_api/content/v21/model/returnaddress_custom_batch_response.ex.
Writing ReturnaddressCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/returnaddress_custom_batch_response_entry.ex.
Writing ReturnaddressListResponse to clients/content/lib/google_api/content/v21/model/returnaddress_list_response.ex.
Writing ReturnpolicyCustomBatchRequest to clients/content/lib/google_api/content/v21/model/returnpolicy_custom_batch_request.ex.
Writing ReturnpolicyCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/returnpolicy_custom_batch_request_entry.ex.
Writing ReturnpolicyCustomBatchResponse to clients/content/lib/google_api/content/v21/model/returnpolicy_custom_batch_response.ex.
Writing ReturnpolicyCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/returnpolicy_custom_batch_response_entry.ex.
Writing ReturnpolicyListResponse to clients/content/lib/google_api/content/v21/model/returnpolicy_list_response.ex.
Writing Row to clients/content/lib/google_api/content/v21/model/row.ex.
Writing Service to clients/content/lib/google_api/content/v21/model/service.ex.
Writing SettlementReport to clients/content/lib/google_api/content/v21/model/settlement_report.ex.
Writing SettlementTransaction to clients/content/lib/google_api/content/v21/model/settlement_transaction.ex.
Writing SettlementTransactionAmount to clients/content/lib/google_api/content/v21/model/settlement_transaction_amount.ex.
Writing SettlementTransactionAmountCommission to clients/content/lib/google_api/content/v21/model/settlement_transaction_amount_commission.ex.
Writing SettlementTransactionIdentifiers to clients/content/lib/google_api/content/v21/model/settlement_transaction_identifiers.ex.
Writing SettlementTransactionTransaction to clients/content/lib/google_api/content/v21/model/settlement_transaction_transaction.ex.
Writing SettlementreportsListResponse to clients/content/lib/google_api/content/v21/model/settlementreports_list_response.ex.
Writing SettlementtransactionsListResponse to clients/content/lib/google_api/content/v21/model/settlementtransactions_list_response.ex.
Writing ShipmentInvoice to clients/content/lib/google_api/content/v21/model/shipment_invoice.ex.
Writing ShipmentInvoiceLineItemInvoice to clients/content/lib/google_api/content/v21/model/shipment_invoice_line_item_invoice.ex.
Writing ShipmentTrackingInfo to clients/content/lib/google_api/content/v21/model/shipment_tracking_info.ex.
Writing ShippingSettings to clients/content/lib/google_api/content/v21/model/shipping_settings.ex.
Writing ShippingsettingsCustomBatchRequest to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_request.ex.
Writing ShippingsettingsCustomBatchRequestEntry to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_request_entry.ex.
Writing ShippingsettingsCustomBatchResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_response.ex.
Writing ShippingsettingsCustomBatchResponseEntry to clients/content/lib/google_api/content/v21/model/shippingsettings_custom_batch_response_entry.ex.
Writing ShippingsettingsGetSupportedCarriersResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_get_supported_carriers_response.ex.
Writing ShippingsettingsGetSupportedHolidaysResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_get_supported_holidays_response.ex.
Writing ShippingsettingsGetSupportedPickupServicesResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_get_supported_pickup_services_response.ex.
Writing ShippingsettingsListResponse to clients/content/lib/google_api/content/v21/model/shippingsettings_list_response.ex.
Writing Table to clients/content/lib/google_api/content/v21/model/table.ex.
Writing TestOrder to clients/content/lib/google_api/content/v21/model/test_order.ex.
Writing TestOrderLineItem to clients/content/lib/google_api/content/v21/model/test_order_line_item.ex.
Writing TestOrderLineItemProduct to clients/content/lib/google_api/content/v21/model/test_order_line_item_product.ex.
Writing TransitTable to clients/content/lib/google_api/content/v21/model/transit_table.ex.
Writing TransitTableTransitTimeRow to clients/content/lib/google_api/content/v21/model/transit_table_transit_time_row.ex.
Writing TransitTableTransitTimeRowTransitTimeValue to clients/content/lib/google_api/content/v21/model/transit_table_transit_time_row_transit_time_value.ex.
Writing UnitInvoice to clients/content/lib/google_api/content/v21/model/unit_invoice.ex.
Writing UnitInvoiceAdditionalCharge to clients/content/lib/google_api/content/v21/model/unit_invoice_additional_charge.ex.
Writing UnitInvoiceTaxLine to clients/content/lib/google_api/content/v21/model/unit_invoice_tax_line.ex.
Writing Value to clients/content/lib/google_api/content/v21/model/value.ex.
Writing Weight to clients/content/lib/google_api/content/v21/model/weight.ex.
Writing Accounts to clients/content/lib/google_api/content/v21/api/accounts.ex.
Writing Accountstatuses to clients/content/lib/google_api/content/v21/api/accountstatuses.ex.
Writing Accounttax to clients/content/lib/google_api/content/v21/api/accounttax.ex.
Writing Datafeeds to clients/content/lib/google_api/content/v21/api/datafeeds.ex.
Writing Datafeedstatuses to clients/content/lib/google_api/content/v21/api/datafeedstatuses.ex.
Writing Liasettings to clients/content/lib/google_api/content/v21/api/liasettings.ex.
Writing Localinventory to clients/content/lib/google_api/content/v21/api/localinventory.ex.
Writing Orderinvoices to clients/content/lib/google_api/content/v21/api/orderinvoices.ex.
Writing Orderreports to clients/content/lib/google_api/content/v21/api/orderreports.ex.
Writing Orderreturns to clients/content/lib/google_api/content/v21/api/orderreturns.ex.
Writing Orders to clients/content/lib/google_api/content/v21/api/orders.ex.
Writing Pos to clients/content/lib/google_api/content/v21/api/pos.ex.
Writing Products to clients/content/lib/google_api/content/v21/api/products.ex.
Writing Productstatuses to clients/content/lib/google_api/content/v21/api/productstatuses.ex.
Writing Pubsubnotificationsettings to clients/content/lib/google_api/content/v21/api/pubsubnotificationsettings.ex.
Writing Regionalinventory to clients/content/lib/google_api/content/v21/api/regionalinventory.ex.
Writing Returnaddress to clients/content/lib/google_api/content/v21/api/returnaddress.ex.
Writing Returnpolicy to clients/content/lib/google_api/content/v21/api/returnpolicy.ex.
Writing Settlementreports to clients/content/lib/google_api/content/v21/api/settlementreports.ex.
Writing Settlementtransactions to clients/content/lib/google_api/content/v21/api/settlementtransactions.ex.
Writing Shippingsettings to clients/content/lib/google_api/content/v21/api/shippingsettings.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs
fixing file permissions
2020-05-12 05:09:47,312 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/content/synth.metadata'
2020-05-12 05:09:47 [ERROR] Synthesis failed
2020-05-12 05:09:47,350 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/content/synth.metadata', 'synth.py', '--', 'Content']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Prevent auto loading of css

Is there a way to not automatically include the css file? I would like to create my own styling, and the auto-import of the stylesheet makes this harder than strictly required.

The autoloading also makes the module incompatible with Next.js.
Next.js does not allow css imports from within the module.
Getting this error:

done in 2.0.0


fix: prevent map not found error in scene change generation trigger

Closes #88

Included in 3.2.1.


Inconsistency in TRX logging between .NET Core 3.1.103 and 3.1.300

Description
The TRX logs are different between .NET Core 3.1.103 and 3.1.300. We noticed while relying on the output in the VSCode .NET Test Explorer extension: https://github.com/formulahendry/vscode-dotnet-test-explorer/issues/267
Steps to reproduce

Clone this repo: https://github.com/formulahendry/vscode-dotnet-test-explorer/
cd to this folder: https://github.com/formulahendry/vscode-dotnet-test-explorer/tree/master/test/xunittests
Run dotnet test --no-build --logger "trx;LogFileName=testResultsXml.trx" --filter "FullyQualifiedName=XunitTests.TestClass3.Fail" in both versions of the .NET Core SDK

Expected behavior
The generated TRX file follows some kind of specification and is consistent.
Actual behavior
The TRX file differs. The output for .NET Core 3.1.103 is:
<TestDefinitions>
  <UnitTest name="XunitTests.TestClass3.Fail(value: 2)" storage="/path/to/the/repo/vscode-dotnet-test-explorer/test/xunittests/bin/debug/netcoreapp3.1/xunittests.dll" id="5d23175e-8479-779f-39f4-23aa2608428b">
    <Execution id="285b15ac-175b-4204-8d35-32dab901e73d" />
    <TestMethod codeBase="/path/to/the/repo/vscode-dotnet-test-explorer/test/xunittests/bin/Debug/netcoreapp3.1/XunitTests.dll" adapterTypeName="executor://xunit/VsTestRunner2/netcoreapp" className="XunitTests.TestClass3" name="XunitTests.TestClass3.Fail(value: 2)" />
  </UnitTest>
</TestDefinitions>

while .NET Core 3.1.300 returns:
<TestDefinitions>
    <UnitTest name="XunitTests.TestClass3.Fail(value: 2)" storage="d:\SomePath\vscode-dotnet-test-explorer\test\xunittests\bin\debug\netcoreapp3.1\xunittests.dll" id="5d23175e-8479-779f-39f4-23aa2608428b">
      <Execution id="ceaf151e-e91c-4f92-ba85-4af475de7c28" />
      <TestMethod codeBase="d:\SomePath\vscode-dotnet-test-explorer\test\xunittests\bin\Debug\netcoreapp3.1\XunitTests.dll" adapterTypeName="executor://xunit/VsTestRunner2/netcoreapp" className="XunitTests.TestClass3" name="Fail" />
    </UnitTest>
  </TestDefinitions>

Note the differences in TestDefinitions/UnitTest/TestMethod/@name.
Environment
Happens under both Windows and Linux.
Actual question
On which behaviour should we rely in the future? What string is supposed to be contained in UnitTest/TestMethod/@name and UnitTest/@name? Is there documentation about this somewhere?

@GeorchW Rely on .NET Core 3.1.300 version. There is no documentation on it, but you can look at the change : https://github.com/microsoft/vstest/pull/2355 @nohwnd

Okay, can you tell me what value TestDefinitions/UnitTest/@name contains? Is it just the un-split test method name? Or is it possible for a UnitTest node to contain multiple TestMethods?

TestDefinitions/UnitTest/@name - contains name of the test method. UnitTest contains only one TestMethod.


Issues with address-merger and FQDN to parent DG

HI Sven -
For address-merging, I can’t seem to move ipv4 objects from a child DG to a parent DG where a FQDN exists (the object names are the same).
Result (whether I use pickfilter = ipv4 or fqdn)

value 'ip-netmask-x.x.x.x'

keeping object '/x/AddressStore/Address:somefqdnname'

object 'somefqdnname' 'fqdn' cannot be merged because it has an ancestor with different value
ancestor name: 'somefqdnname' DG: 'someDG'  value: 'somefqdnvalue'

Commands attempted –
pan-os-php in=api://x.x.x.x type=address-merger actions=move:tosomezone-name location=fromsomezonename allowmergingwithupperlevel 'pickfilter=(object is.fqdn)'
pan-os-php in=api://x.x.x.x type=address-merger actions=move:tosomezone-name location=fromsomezonename allowmergingwithupperlevel 'pickfilter=(object is.ipv4)'
pan-os-php in=api://x.x.x.x type=address-merger actions=move:tosomezone-name location=fromsomezonename 'pickfilter=(object is.fqdn)'
Hierarchy –
tosomezone-name

fromsomezonename

you scrambled a lot of commands:
pan-os-php type=address-merger - does not have argument "actions", where do you get this from?
If you are checking the help information you will find an argument called:
DupAlgorithm=SameAddress; which is predefined and used;
What you are searching is more or less a new DupAlgorithm=SameName;
If I remember correct, then you were requesting something similar for tag-merger

FR: add DupAlgorithm=SameName so that objects with same name get merged with fqdn objects

but there is for you also another feature available;
pan-os-php type=address actions=value-set-ip-for-fqdn

value-set-ip-for-fqdn     | - replace FQDN with the IP
===========================
value-set-reverse-dns     | - replace IP with the FQDN

You're probably right Sven, I'll check it again. I tried a lot of things.
Thanks

Sven,
2 commands got me where I wanted to be -

First running type=address actions=value-set-reverse-dns (this converted child DG objects from ipv4 to fqdn)
Then running type=address-merger DupAlgorithm=sameaddress moved the objects to the parent DG as I had wanted all along.

If 'samename' could be incorporated into address-merger like with tag-merger, it would be very helpful.
Thanks for your work.


Investigate adding very simple monitoring to make sure pep8speaks server is up and running.

The problem statement is to ensure the pep8speaks server has not stopped working and notify via email if the backend is not working.

@tushar5526 Working on this.

@tushar5526 status page link, should I add to README.md


Bump a few packages related to the Matrix ecosystem

Motivation for this change

Updated element-{web,desktop} to 1.7.4 (https://github.com/vector-im/element-web/releases/tag/v1.7.4, https://github.com/vector-im/element-desktop/releases/tag/v1.7.4).
Updated matrix-synapse to 1.19.0.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test matrix-synapse

Result of nixpkgs-review pr 95708 1

7 packages built:
- element-desktop
- matrix-synapse
- matrixcli
- python37Packages.canonicaljson
- python37Packages.signedjson
- python38Packages.canonicaljson
- python38Packages.signedjson

Ported to stable as 43e11555d0d7be230db08f266145eb1711b7364c, 32324de6d2b6db2bbd335ede2ad8d5898d77b175, af10edeb40f56240d9fe5e59bdbaa2fa9766bf4b, f0924dbf552e28ee0462b180116135c187eb41b4.


Multiple Location headers in response are concatenated

tested with requests 2.9
when a http server resonds with multiple Location headers in 301 redirect the locations are concatenated
eg
Location: http://foo.com
Location: http://foo.com
results in a redirect to
"http://foo.com,http://foo.com"
pretty sure this behavior is not present in any other http clients

A web server MUST NOT respond with multiple location header fields. From RFC 7320 Section 3.2.2:

A sender MUST NOT generate multiple header fields with the same field name in a message unless either the entire field value for that header field is defined as a comma-separated list [i.e., #(values)] or the header field is a well-known exception (as noted below).

There is exactly one well-known exception: Set-Cookie. Location is not Set-Cookie, so that doesn't apply. So it would only be acceptable to send multiple Location headers if the syntax allowed multiple comma-separated values. Location is defined in RFC 7231 Section 7.1.2:

Location = URI-reference
The field value consists of a single URI-reference.

The server in this example is violating the HTTP specification. In the face of such violation, a user-agent is simply not required to take any specific action. In particular, while the example you provided above has a very simple course of action (both URLs are the same), if both URLs were not the same requests would be unable to take any sensible action: the situation is too ambiguous to allow a correct decision.
At the level of requests actually catching this and treating it as an error condition is tricky, because requests only sees the header string http://foo.com,http://foo.com, which perversely does parse as a valid URL in the case of most Python libraries because in principle the comma is an allowed character in the host part of the URL. This puts us in a bit of a bind. However, urllib3's HTTPHeaderDict structure could enforce this requirement and treat this case as an error on receiving it. That might be a sensible way to go, but it's us going out of our way to provide a slightly nicer error when a server does something it really really shouldn't do. @sigmavirus24, thoughts?

I guess then the web server is doing this to break python-urllib clients as it does not seem to affect web browsers or curl

@L2501 To be clear, we could handle this case. I just don't think we should. The server is very wrong, and it is not our job to work around the failures of that server. In this instance there is a clear acceptable solution, but the general case is not solve able. We can handle this, and we're looking at how best to do that, but if you want to find someone to blame (and your tone suggests you do) then I recommend directing your blame at the website operator whose website is broken, rather than us.

Well i just expected it to only count the first header and igonre the rest to prevent CRLF Injection attacks...

Yes, @L2501. Please continue to act aggressively towards us for not having encountered such a poorly configured server. Please don't take any action to correct that server.

@Lukasa There was a proposed version of the Header Dict that ignored multiple headers for anything other Set-Cookie headers. We could fix this faster in requests by using .getlist on the original Header Dict from urllib3 and throwing an exception if it returns more than one value.

@L2501 That doesn't prevent CRLF injection attacks, it just keeps functioning in the face of them. My proposed solution above would actually avoid some portion CRLF injection attacks by throwing an exception when an invalid header block is received. Of course, we cannot generally prevent CRLF injection attacks and also re-use TCP connections, so any client that does re-use TCP connections is vulnerable to a well-crafted CRLF injection attack. Generally speaking, defending against CRLF injection attacks is the responsibility of the server operator, not the client.
@sigmavirus24 The better long-term fix might be to promote urllib3's HeaderDict to use in requests. The risk with doing it your way is that we assume that the raw object exists and is a urllib3 one. I suppose we could have a conditional path that attempts to use urllib3's but falls back to using ours.
We could in fact do that, and then plan in 3.0.0 to promote urllib3's HeaderDict to use in requests which would allow us to remove the conditional code path in 3.0.0.

The risk with doing it your way is that we assume that the raw object exists and is a urllib3 one.

Are you thinking about a potential AppEngineAdapter case where it returns an object that is nothing like urllib3 and further breaks urllib3's contract? We can fix this on the adapter level for requests instead of making requests handle that complexity through a whole lot of conditional cases.

@sigmavirus24 No, I'm thinking of test libraries or anything else that returns a Response object from the HTTPAdapter that is not actually backed by a urllib3 response object.

@Lukasa I'm not as concerned about them. Any test library that hasn't been half-written and thrown up on PyPI will handle this just fine (requests-mock, betamx, vcrpy, all do just fine).

@sigmavirus24 Be that as it may, in general our code assumes that .raw may not come from urllib3, and we should endeavour to maintain that if possible.

So, that code was added in https://github.com/kennethreitz/requests/pull/1425 but there wasn't much justification provided at the time for having a conditional like that. The only other remotely similar piece of the library that I'm aware of is our cookie handling which just refuses to do anything if it isn't anything like a urllib3 response.
We've held an illusion of urllib3 being an "implementation" detail but never supported anything other than that in reality. The likelihood that the raw response will not be a urllib3 object seems very close to 0 to me, but I'm open to being convinced otherwise.

@sigmavirus24 The common situation is where the response object is StringIO or something similar. I think going out of our way to avoid breaking that is a good idea. If we were going straight to 3.0.0 I'd be fine with breaking it, but ideally we'd deal with this sooner.

The common situation is where the response object is StringIO or something similar.

I understand we're hoping to catch the case where it's more file-like than urllib3.HTTPResponse like, but I'm not sure how common that case is, is what I'm saying.
I also don't want to just remove support for this, but I'd like to see much better encapsulation of these shims honestly.

Agreed, I don't think we've done well enough in the past, but sadly I also don't think that's an excuse for making the mistake here. We know it's a risk, we should account for it.
That said, it's also fairly easy to have a fallback.

@sigmavirus24

There was a proposed version of the Header Dict that ignored multiple headers for anything other Set-Cookie headers. We could fix this faster in requests by using .getlist on the original Header Dict from urllib3 and throwing an exception if it returns more than one value.

This would break the list-like headers though? The ones defined as #(values), which RFC 7230 permits to split into multiple fields.

@vfaronov That isn't being proposed in general, it's being proposed purely for the Location header.

Supporting multiple location headers is /not/ valid practice, see [here], and should be rejected.
However, supporting multiple headers in general is valid as per RFC2616, and requests should support that, see here.

@foxx I appreciate that you were trying to be helpful, but please read the discussion on this issue before commenting. If you look at the first comment in this issue you'll see that it begins with:

A web server MUST NOT respond with multiple location header fields.

The proposed action in this thread is that requests should error on this condition, rather than doing what it currently does which is to attempt to parse the multiple Location fields as though they were one. Note also that that behaviour means that requests already does support multiple headers.
Finally, RFC 2616 is deprecated. RFC 7230 and RFC 7231 have replaced it. =)

please read the discussion on this issue before commenting.

Fwiw, I'd spent about 10 minutes reading through and researching before I posted, but it looks like I misread some of the further comments, apologies.

The proposed action in this thread is that requests should error on this condition

Given that the RFCs are pretty clear on the situation of multiple Location headers, e.g. MUST NOT, I would have thought the default would be to raise a parser error?

Finally, RFC 2616 is deprecated. RFC 7230 and RFC 7231 have replaced it. =)

Oh dang, my bad.

Yeah, that would be ideal, but we don't own the parser: we use httplib. That's a source of ongoing frustration, but the upshot is that we have to do this validation higher up the stack, in requests itself, and the nature of the datastructures and relationships used make it somewhat tricky to do that.

Actually just been thinking some more about this, and perhaps it makes more sense for requests to follow what the majority of other libraries and browsers are doing? Merging these multiple headers is certainly not the correct behaviour, but I'm not sure what the alternative should be.
In use cases where requests is being used as a scraper, you'd expect requests to behave in the same way as the browser, this is despite the RFCs treating multiple location headers with the same severity as a missing header colon.
Some relevant details here, and here.
Apparently chrome throws an error, as does Firefox.
Error code: ERR_RESPONSE_HEADERS_MULTIPLE_LOCATION

If the major browsers are throwing errors, then perhaps requests should too?
Thoughts?

Just tried this myself in Chrome;

That would be a 3.0 change but I'm amenable to that. @Lukasa, what about you?

I think that's what was already proposed here. =)

We should consider the possibility of raising this error only if we are following redirects (e.g. utilizing the Location header). If the Location header isn't going to trigger any automatic behavior in the client, then perhaps representing the (broken) multiple headers the way we do is okay, as it would allow the user to still access to resource, instead of making it impossible.

Yup, the error would be raised in the resolve_redirects code?

@kennethreitz Yup agreed

This was fixed in 3.0 by #3417. I'm closing this as a result and tagging the correct milestone for it.


arrow keys should navigate while in commit edit window.

When I am editing a commit, I am not able to navigate via the arrow keys.  If a want to fix a misspelled word I must use backspace.

I've finding a proper solution. We can using https://github.com/slap-editor component but it's very big project than GC. So, maybe I need to implement cursor behavior simply.

I made a patch of blessed for this. https://github.com/chjj/blessed/pull/156
When this patch will be approved, it'll be fixed.


"Deployment Options" changed to "Deployment Center" in Azure Portal

Under section "Disconnect local Git deployment" and step #2 Click "Deployment options".
The naming is changed. It is called "Deployment Center" now in Azure Portal. Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ec897b11-5ad4-a660-598c-daa98d81c536
Version Independent ID: d4f12beb-b256-ab36-80f1-50c8207b0b1e
Content: Continuous integration and deployment - DevOps with ASP.NET Core and Azure
Content Source: aspnetcore/azure/devops/cicd.md
Product: aspnet-core
GitHub Login: @CamSoper
Microsoft Alias: scaddie

Any chance you could PR this? At the top right of the article, select the pen icon:

Select the pen icon again. Save.


There is no fetch_all_data.sh file in ./data

fetch_all_data.sh and corresponding files have been added. Sorry about that!