},
  {
    "input": "-x.ß",
    "output": "-x.xn--zca"
  },
  {
    "comment": "Label with trailing hyphen",
    "input": "x-.xn--zca",
    "output": "x-.xn--zca"
  },
  {
    "input": "x-.ß",
    "output": "x-.xn--zca"
  },
  {
    "comment": "Empty labels",
    "input": "x..xn--zca",
    "output": "x..xn--zca"
  },
  {
    "input": "x..ß",
    "output": "x..xn--zca"
  },

            state.errorHandled = true;
            var errorMessage = config.labels.error;
            try {
                var data = JSON.parse(e.data);
                if (data.errorCode && config.labels.errors && config.labels.errors[data.errorCode]) {
                    errorMessage = config.labels.errors[data.errorCode];
                } else if (data.message) {

    attributes:
      label: Why do we need it to be improved?
    validations:
      required: true

  - type: textarea
    attributes:
      label: Example
      description: >
        Please provide an example usage of the feature that would be different with the improvement.
      render: java
    validations:
      required: true

  - type: textarea
    attributes:
      label: Current Behavior

    //                                                                       Resolve Label
    //                                                                       =============
    protected String resolveLabelIfNeeds(final MessageManager messageManager, final Locale locale, final String label) {
        return label.startsWith("labels.") ? messageManager.getMessage(locale, label) : label;
    }

- `mimetype` - MIME type (default: text/html)
- `filetype` - File extension (default: html)
- `created` - Creation timestamp
- `timestamp` - Last modified timestamp
- `boost` - Document boost factor
- `label` - Access control labels
- Custom fields as defined in your configuration

**Response**:
```json
{
  "response": {
    "status": 0,
    "message": "Successfully imported 2 documents"
  }
}
```

start by trying one of the smaller/easier issues here i.e.
[issues with the "good first issue" label](https://github.com/tensorflow/tensorflow/labels/good%20first%20issue)
and then take a look at the
[issues with the "contributions welcome" label](https://github.com/tensorflow/tensorflow/labels/stat%3Acontributions%20welcome).
These are issues that we believe are particularly well suited for outside

	pc            int64 // virtual PC; count of Progs; doesn't advance for GLOBL or DATA.
	input         []lex.Token
	inputPos      int
	pendingLabels []string // Labels to attach to next instruction.
	labels        map[string]*obj.Prog
	toPatch       []Patch
	addr          []obj.Addr
	arch          *arch.Arch
	ctxt          *obj.Link
	firstProg     *obj.Prog
	lastProg      *obj.Prog

    validations:
      required: false

  - type: checkboxes
    id: related-idea
    attributes:
      label: "Related Idea"
      options:
        - label: "Has this idea, or one like it, been proposed before?"
        - label: "Does this affect error handling?"
        - label: "Is this about generics?"
        - label: "Is this change backward compatible? Breaking the Go 1 compatibility guarantee is a large cost and requires a large benefit"

	if p.firstProg == nil {
		p.firstProg = prog
	} else {
		p.lastProg.Link = prog
	}
	p.lastProg = prog
	if doLabel {
		p.pc++
		for _, label := range p.pendingLabels {
			if p.labels[label] != nil {
				p.errorf("label %q multiply defined", label)
				return
			}
			p.labels[label] = prog
		}
		p.pendingLabels = p.pendingLabels[0:0]
	}
	prog.Pc = p.pc
	if *flags.Debug {
		fmt.Println(p.lineNum, prog)
	}

     * Spec change:
        * Deployment’s [selector](http://kubernetes.io/docs/user-guide/labels/#label-selectors) is now more general (supports set-based selector; it only supported
equality-based selector in 1.1).
        * .spec.uniqueLabelKey is removed -- users can’t customize unique label key --
and its default value is changed from
“deployment.kubernetes.io/podTemplateHash” to “pod-template-hash”.