I think it's wrong.（我觉得文档是不是写错了）

From: Vue Guide - Components #data Must Be a Function
What is the meaning of "The el option also requires a function value when used in a component instance, for exactly the same reason."?
"The el option also requires a function value when used in a component instance, for exactly the same reason."这句话是什么意思？和上下文完全不通顺。el也不会是一个函数。
From: Vuex - Mutations #Mutations Follow Vue's Reactivity Rules
What is the meaning of "Use Vue.set(obj, 'newProp', 123), or -"?(I don't know '-')
"Use Vue.set(obj, 'newProp', 123), or -"中的'-'是什么意思？
I think it's wrong.
我觉得文档是不是写错了。

结合最上边一行data Must Be a Function，
那么  这句话的翻译就是，“当被用在实例化组件中，el选项也需要函数类型的值，正是基于同样地原因(同data用function的原因)”。

我一开始也是这么想的。但是看了下文档，el是字符串，而且这里和上下文完全没有关联。

Thank your for your interest in this project.
However, your issue is a usage/support question, and the issue tracker is reserved exclusively for bug reports and feature requests.
We encourage you to ask it on the forum  (has a chinese section), Stack Overflow or on gitter and are happy to help you out there.

Thank you...
But You do not understand what I mean. This may be a problem with the documentation.
We have already discussed, el can not be a function value.

Oh, you are right, sorry!
Thank you for bringing it up, it must be a left-over fragment from the old 1.0 docs.

"Use Vue.set(obj, 'newProp', 123), or -"
I think ", or -" is also superfluous.
@LinusBorg

it can be left out, but is fine, in general. it'd connecting the two list points: "You can use Vue.set(), or - you can replace the object ..."

Well, why not make it like this?

Use Vue.set(obj, 'newProp', 123).
Or replace that Object with a fresh one. For example, using the stage-2 object spread syntax we can write it like this:

@dear-lizhihua Thanks for reporting these! The issue with the core documentation is resolved now, so I'm closing this. To further discuss the remaining Vuex documentation issue you have, can you open up a new issue on the Vuex repo? Vuex and Vue Router host their own documentation.

Oh, I'm sorry. Thank you!


X86 Binary required for 32 bit linux

Hello sir can you give me binary X86 Binarylinux

You can go to the release page to download the binary.
Both server and client binary are in the "sufttun-linux-386.tar.gz".


pull request for e2e test at 12/25/2016 14:45:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Monitor pod status in submission v2.

Allows the submission client to remain running until the driver pod completes. This comprises a number of refactors to allow the pod monitoring to be mocked in a unit test, and also includes a variant of #282 so that both V1 and V2 can have the exit code of the containers be logged at the end of the running application.

@lins @ash211

Note that this approach differs in some key ways from #282. The statuses of all containers are logged without necessarily assuming the driver container is the only container, although it's more than likely that there will only be one container here. The status of the containers are described without an assumption that they are necessarily in the "FINISHED" state. Finally, the logging itself is built into the new LoggingPodStatusWatcher#awaitCompletion API which also makes it such that callers do not need to maintain their own CountDownLatch as well as not needing to worry about separately asking the Watcher to log the final status.
It would be good to compare this with #282 and combine the best aspects of each.


Pic

@fgregg - I did not merge this branch into master, since I wanted to see how any edits to Councilmatic core might affect this.
We still need to make these edits here (not Councilmatic core). Why? The edits for LA Metro related to a custom filter for agenda_urls, not a model property, as they do with Councilmatic core (for the Bill model).
Am I understanding this correctly? And also, if this works well, then can we deploy your changes in the property-image-cache to production?


feat: allow configuring auth token using UNLEASH_AUTH_TOKEN env

About the changes

This change introduces the possibility of configuring the auth token using UNLEASH_AUTH_TOKEN, instead of AUTH_TOKEN. This is useful when using a bunch of providers, to be able to more easily keep track of which env variables are used where, and avoid conflicts with other providers.

Closes #90

Important files

Discussion points

To avoid a breaking change I changed the configValue so it cloud take multiple values for env variables, and "selects" the first non-empty one. I also saw that configValue.ValueString() returns "" when configValue.IsNull() == true (for the case where no env variable is set and configValue.IsNull() == true), so I think it still keeps its old behaviour.
Maybe the more "specific" UNLEASH_AUTH_TOKEN should be before AUTH_TOKEN so the more specific version if prioritized, in case another provider uses the AUTH_TOKEN variable?

@JonasBak Thanks you!
Can we unit-test it? This would better document the expected behavior.
func Test_provider_configValue(t *testing.T) {
	t.Setenv("FOO", "foo")
	t.Setenv("BAR", "bar")
	t.Setenv("BAZ", "baz")
	assert.Equal(t, "foo", configValue(types.StringValue("foo"), "bar"))
	assert.Equal(t, "", configValue(types.StringValue(""), "SOME_ENV"))
	assert.Equal(t, "bar", configValue(types.StringValue(""), "BAR"))
	assert.Equal(t, "baz", configValue(types.StringValue(""), "QUX", "BAZ"))
}

Thanks for the feedback 🙌 I added a test as you suggested.


fixes unused-ignore errors under mypy 1.10

Short description
This PR proposes to increased developer happiness by fixing these type errors occurring under mypy v1.10.0. This is the version that we require in our pyproject.toml.

It's now part of https://github.com/dlt-hub/verified-sources/pull/545


Fix for when version query returns malformed version

Pull Request Checklist

Description

Fix version comparison logic to be a bit more resilient so that if the version returned is not expected the code does not raise exceptions.
Some of the unit test changes were to address the unit tests essentially testing nothing and not being really valid tests.
Related Issue

Fixes #1278

Released in v5.2.1


Unable to work --lib flag with dom

Note: v1.9.0-dev.20160407 works fine, but v1.9.0-dev.20160408 is broken.
TypeScript Version:
master
Code
var a: HTMLAnchorElement;
var b: HTMLPhraseElement;

Expected behavior:
$ node built/local/tsc.js --lib es5,dom index.ts

Actual behavior:
$ node built/local/tsc.js --lib es5,dom index.ts
index.ts(2,8): error TS2304: Cannot find name 'HTMLPhraseElement'.

HTMLPhraseElement is an IE specific definition, and does not exist in the standard. newer version of Edge stopped supporting it as well. It has been removed in https://github.com/Microsoft/TypeScript/pull/7619 as part of updating the DOM.
Please note this is not specific to --lib, it just does not exist in the DOM definitions any more.
to keep using it, please add the definitions:
interface HTMLPhraseElement extends HTMLElement {
    /**
      * Sets or retrieves reference information about the object.
      */
    cite: string;
    /**
      * Sets or retrieves the date and time of a modification to the object.
      */
    dateTime: string;
}

declare var HTMLPhraseElement: {
    prototype: HTMLPhraseElement;
    new(): HTMLPhraseElement;
}

Thanks.