[SPARK-28083][SQL] Support LIKE ... ESCAPE syntax

What changes were proposed in this pull request?
The syntax 'LIKE predicate: ESCAPE clause' is a ANSI SQL.

Note: If the input string or pattern string is null, then the result is null too.
There are some mainstream database support the syntax.
PostgreSQL:
https://www.postgresql.org/docs/11/functions-matching.html
Vertica:
https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/SQLReferenceManual/LanguageElements/Predicates/LIKE-predicate.htm?zoom_highlight=like escape
MySQL:
https://dev.mysql.com/doc/refman/5.6/en/string-comparison-functions.html
Oracle:
https://docs.oracle.com/en/database/oracle/oracle-database/19/jjdbc/JDBC-reference-information.html#GUID-5D371A5B-D7F6-42EB-8C0D-D317F3C53708
https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/Pattern-matching-Conditions.html#GUID-0779657B-06A8-441F-90C5-044B47862A0A
How was this patch tested?
Exists UT and new UT.

Test build #106996 has started for PR 25001 at commit 4f5016a.

Test build #106996 has finished for PR 25001 at commit 4f5016a.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Like(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106996/
Test FAILed.

Can one of the admins verify this patch?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12194/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12196/
Test PASSed.

Test build #106999 has started for PR 25001 at commit 8609a46.

Test build #106999 has finished for PR 25001 at commit 8609a46.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106999/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12197/
Test PASSed.

Test build #107001 has started for PR 25001 at commit 8992b5a.

Test build #107001 has finished for PR 25001 at commit 8992b5a.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107001/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12206/
Test PASSed.

Test build #107012 has started for PR 25001 at commit c9d7dfe.

Test build #107012 has finished for PR 25001 at commit c9d7dfe.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107012/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12207/
Test PASSed.

Test build #107013 has started for PR 25001 at commit b5be74a.

Test build #107013 has finished for PR 25001 at commit b5be74a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107013/
Test FAILed.

Also, you need to update docs/sql-keywords.md

@maropu Thanks for you reminder. I have added keyword.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12285/
Test PASSed.

Test build #107105 has started for PR 25001 at commit 6ac3f21.

Test build #107105 has finished for PR 25001 at commit 6ac3f21.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107105/
Test FAILed.

@maropu Could you tell me the reason the leatest Test build failure. I can't find the source code.

@beliefer Please re-generate golden files.
org.scalatest.exceptions.TestFailedException: Expected "...(1 AS STRING) LIKE %[]:boolean>", but got "...(1 AS STRING) LIKE %[ \]:boolean>" Schema did not match for query #39 select 1 like '%' FROM t: QueryOutput(select 1 like '%' FROM t,struct<CAST(1 AS STRING) LIKE % \:boolean>,true)

https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/107105/testReport/org.apache.spark.sql/SQLQueryTestSuite/sql/

Please use the following command to rebuild the golden answer files.
SPARK_GENERATE_GOLDEN_FILES=1 build/sbt "sql/test-only *SQLQueryTestSuite"

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12342/
Test PASSed.

Test build #107172 has started for PR 25001 at commit 5303564.

Test build #107172 has finished for PR 25001 at commit 5303564.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

@wangyum @dongjoon-hyun Thanks for all your help and review.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107172/
Test PASSed.

Test build #107226 has started for PR 25001 at commit a0ceae1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12386/
Test PASSed.

Test build #107227 has started for PR 25001 at commit 28a566d.

Test build #107226 has finished for PR 25001 at commit a0ceae1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107226/
Test PASSed.

Test build #107227 has finished for PR 25001 at commit 28a566d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107227/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12407/
Test PASSed.

Test build #107257 has started for PR 25001 at commit 9509c73.

Test build #107257 has finished for PR 25001 at commit 9509c73.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Like(left: Expression, right: Expression, escapeCharOpt: Option[String] = None)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107257/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12423/
Test PASSed.

Test build #107274 has started for PR 25001 at commit 0bcb027.

Test build #107274 has finished for PR 25001 at commit 0bcb027.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107274/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12427/
Test PASSed.

Test build #107279 has started for PR 25001 at commit b5a3cc7.

Test build #107279 has finished for PR 25001 at commit b5a3cc7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107279/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12447/
Test PASSed.

Test build #107301 has started for PR 25001 at commit 56f5f8a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12449/
Test PASSed.

Test build #107303 has started for PR 25001 at commit 7fd5a7f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12450/
Test PASSed.

Test build #107304 has started for PR 25001 at commit 0650ef8.

Test build #107304 has finished for PR 25001 at commit 0650ef8.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107304/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12451/
Test PASSed.

Test build #107305 has started for PR 25001 at commit 479e24a.

Test build #107305 has finished for PR 25001 at commit 479e24a.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107305/
Test FAILed.

Test build #107301 has finished for PR 25001 at commit 56f5f8a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107301/
Test PASSed.

Test build #107303 has finished for PR 25001 at commit 7fd5a7f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107303/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12453/
Test PASSed.

Test build #107307 has started for PR 25001 at commit 103203f.

Test build #107307 has finished for PR 25001 at commit 103203f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107307/
Test PASSed.

@maropu Could you continue to take a look at this PR ？

Retest this please.

Test build #107480 has started for PR 25001 at commit 103203f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12610/
Test PASSed.

Test build #107480 has finished for PR 25001 at commit 103203f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107480/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12640/
Test PASSed.

Test build #107514 has started for PR 25001 at commit 33c7ad4.

Test build #107514 has finished for PR 25001 at commit 33c7ad4.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107514/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12645/
Test PASSed.

Test build #107519 has started for PR 25001 at commit 33c7ad4.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12653/
Test PASSed.

Test build #107527 has started for PR 25001 at commit 99bbc2f.

Test build #107519 has finished for PR 25001 at commit 33c7ad4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107519/
Test PASSed.

Test build #107527 has finished for PR 25001 at commit 99bbc2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107527/
Test PASSed.

@maropu Do you here?

yea, I'll check in a day and just a sec.

yea, I'll check in a day and just a sec.

This answer is very interesting.

Also, could you check the query below?
scala> sql("""select * from t8 where a like b escape '"' """).show
org.apache.spark.sql.catalyst.parser.ParseException:
Invalid escape string.Escape string must be empty or one character.(line 1, pos 25)

== SQL ==
select * from t8 where a like b escape '"'
-------------------------^^^

postgres=# select * from t8 where a like b escape '"';
 a | b
---+---
(0 rows)

Also, could you check the query below? Then, plz add some tests in SQLQueryTestSuite.
scala> sql("""select * from t8 where a like b escape '"' """).show
org.apache.spark.sql.catalyst.parser.ParseException:
Invalid escape string.Escape string must be empty or one character.(line 1, pos 25)

== SQL ==
select * from t8 where a like b escape '"'
-------------------------^^^

postgres=# select * from t8 where a like b escape '"';
 a | b
---+---
(0 rows)

It looks like a escape problem. Please use
"select * from t8 where a like b escape '\"' " to test.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12963/
Test PASSed.

Test build #107847 has started for PR 25001 at commit 856242c.

Test build #107847 has finished for PR 25001 at commit 856242c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107847/
Test FAILed.

Test build #108008 has started for PR 25001 at commit 3d01650.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13118/
Test PASSed.

Test build #108008 has finished for PR 25001 at commit 3d01650.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108008/
Test PASSed.

check this query?
scala> sql("""select * from t9 where a like a escape '' """).show
java.lang.AssertionError: assertion failed
	at scala.Predef$.assert(Predef.scala:208)
	at org.apache.spark.sql.catalyst.util.StringUtils$.escapeLikeRegex(StringUtils.scala:46)
	at org.apache.spark.sql.catalyst.util.StringUtils.escapeLikeRegex(StringUtils.scala)
	at org.apache.spark.sql.catalyst.expressions.GeneratedClass$GeneratedIteratorForCodegenStage1.processNext(Unknown Source)
	at org.apache.spark.sql.execution.BufferedRowIterator.hasNext(BufferedRowIterator.java:43)

@maropu I'm sorry! I forgot this check and delayed your work. I will Fix this bug.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13140/
Test PASSed.

Test build #108032 has started for PR 25001 at commit 420f1b9.

Test build #108032 has finished for PR 25001 at commit 420f1b9.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108032/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13143/
Test PASSed.

Test build #108035 has started for PR 25001 at commit 2b4c59a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13146/
Test PASSed.

Test build #108038 has started for PR 25001 at commit 9f7707b.

Test build #108035 has finished for PR 25001 at commit 2b4c59a.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108035/
Test FAILed.

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13151/
Test PASSed.

Test build #108043 has started for PR 25001 at commit 9f7707b.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13157/
Test PASSed.

Test build #108049 has started for PR 25001 at commit 24a796e.

Test build #108038 has finished for PR 25001 at commit 9f7707b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108038/
Test PASSed.

Test build #108043 has finished for PR 25001 at commit 9f7707b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108043/
Test PASSed.

Test build #108049 has finished for PR 25001 at commit 24a796e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108049/
Test PASSed.

@maropu Could we continue this PR?

@maropu Are you here?

@yhuai

@shane-huang

Test build #108367 has started for PR 25001 at commit 6b60360.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13462/
Test PASSed.

Test build #108367 has finished for PR 25001 at commit 6b60360.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Like(left: Expression, right: Expression, escapeCharOpt: Option[Char] = None)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108367/
Test FAILed.

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13471/
Test PASSed.

Test build #108376 has started for PR 25001 at commit 6b60360.

Test build #108376 has finished for PR 25001 at commit 6b60360.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Like(left: Expression, right: Expression, escapeCharOpt: Option[Char] = None)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108376/
Test PASSed.

plz uncoment the some existing tests for ESCAPE? https://github.com/apache/spark/blob/4e7a4cd20e2f6e19b45fee6bfd24071ce4c88dd8/sql/core/src/test/resources/sql-tests/inputs/pgSQL/strings.sql#L273

Test build #108549 has started for PR 25001 at commit aa6c785.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13643/
Test PASSed.

plz uncoment the some existing tests for ESCAPE?
https://github.com/apache/spark/blob/4e7a4cd20e2f6e19b45fee6bfd24071ce4c88dd8/sql/core/src/test/resources/sql-tests/inputs/pgSQL/strings.sql#L273

Could I open another PR to resolve this?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13645/
Test PASSed.

Test build #108552 has started for PR 25001 at commit aa0f2f7.

Test build #108552 has finished for PR 25001 at commit aa0f2f7.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #108549 has finished for PR 25001 at commit aa6c785.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108552/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108549/
Test FAILed.

Retest this please.

Test build #108558 has started for PR 25001 at commit aa0f2f7.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13651/
Test PASSed.

Test build #108558 has finished for PR 25001 at commit aa0f2f7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108558/
Test PASSed.

@maropu Could you continue to take a look at this PR?

@maropu Could I open another PR to resolve this?

Since this jira originally intends to support these statements with escape, I think its ok to uncomment them in this pr.

@dongjoon-hyun could you check this pr? (I have no comment now

@maropu Thanks for you reply.

@dongjoon-hyun Could you check this PR?

@maropu @dongjoon-hyun Could you take a look at this PR again? Thanks.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14662/
Test PASSed.

Test build #109608 has started for PR 25001 at commit aa0f2f7.

Seems fine although I haven't taken a close look. Seems somebody (or i) needs to take a closer look for ASNI and if the escaping is done correctly done or not.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14666/
Test PASSed.

Test build #109612 has started for PR 25001 at commit bb0be67.

Test build #109608 has finished for PR 25001 at commit aa0f2f7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109608/
Test PASSed.

Test build #109621 has started for PR 25001 at commit 10f42f4.

@HyukjinKwon Thanks for your review and help me to promote this PR.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14672/
Test PASSed.

Test build #109612 has finished for PR 25001 at commit bb0be67.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #109621 has finished for PR 25001 at commit 10f42f4.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109621/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109612/
Test FAILed.

Retest this please.


fix #3051: fullscreen switching with CTRL+ALT+ENTER doesn't work any …

KeyboardState is defined as:
BOOL KeyboardState[256];
we can't store keysym there, we must use bool
not sure if the fix is correct, the alternative would be to define KeyboardState as
int KeyboardState[256];

@freerdp-bot can you test this, please ?

@abma Nice catch, if you can fix the issue @hardening pointed out. Except this (blocking) remark +1

as far as i can tell, it works for me...


Add FABRIC8CD_GH_TOKEN env variable to planner (and UI builds)

Added this token in npm-build-deliver-cred wrapper.
Resolves https://gitlab.cee.redhat.com/dtsd/housekeeping/issues/1722

@jmelis please review


GCD based, Asynchronous Implementation of the API

This PR contains a GCD DispatchIO based implementation of the API and presumably should scale significantly better than the synchronous one. Throughput should be somewhat worse for obvious reasons.
I also setup a small test server demonstrating the API: http-testserver. Of special interest is the slow handler, which does the typical sleep() async demo.
Unlike Noze.io or Node.js it does not use a single network processing queue, but rather a set of base queues as suggested by Johannes. To support that, the handler API has been enhanced with the queue argument. All API calls of a handler need to be dispatched back to that (but the handler itself runs on the same queue, so the trivial cases require no extra work).
This implementation is supposed to properly support back pressure and pipelining.
Caveats:

tests don't work
little testing has been done, probably has tons of bugs ;-)

It would be awesome if you would get the tests working again. I don't plan to work on such any time soon, so feel free to do anything you want!
Adjusting the tests might be challenging, because, well, they need to be asynchronous. For Noze.io I have a helper class which tries to deal with the asynchronicity, not sure whether it might help you or not (or even whether this is the correct way to test that stuff): NozeIOTestCase.swift
The other hurdle is that I made the HTTPResponseWriter concrete (i.e. it is not a protocol anymore). I suppose that makes some mocking hard. We could change it back to a protocol, but I think it was suggested that we should avoid them for performance reasons.

BTW: I also still wonder whether we would want to allow multiple implementations, or whether that is just bad for a basic core module. E.g. I can imagine that we might be able to use generics to efficiently do something like Apache MPMs, for example:
let asyncServer = HTTPServer<DispatchMPM>(port: ...)

and
let syncServer = HTTPServer<ThreadedMPM>(port: ...)

Both have their unique advantages and disadvantages. But maybe this would make it too complex, not sure.

Adjusting the tests might be challenging, because, well, they need to be asynchronous. For Noze.io I have a helper class which tries to deal with the asynchronicity, not sure whether it might help you or not

Ok. Let me go to work on that, and we'll see how far I get.

I enabled Issues on my fork https://github.com/ZeeZide/http/issues and marked those which may be necessary to merge this PR with a Required for PR label.

@helje5  I added a PR against your fork that has a batch of changes for getting tests to run on the Mac. (There will be another one once I find/fix a bug on Linux).

Don't want to derail this PR, but I think leaking the DispatchQueue the server uses into the handler is mistake. Read and write operations on a descriptor don't need to be synchronized as far as I am aware. An example where the server and handler synchronization primitives are separate can be found here: https://github.com/GeorgeLyon/Server

Don't want to derail this PR, but I think leaking the DispatchQueue the server uses into the handler is mistake.

It is an optimisation. I don't really like it either, but the alternatives seem to expensive to me (require the response-writer to be free-threaded).

Read and write operations on a descriptor don't need to be synchronized as far as I am aware

Yeah, but I don't see how that helps us in any way. The goal here is to allow for asynchronous handlers which support back pressure. That implies more book-keeping. Which needs to be synchronised.
P.S.: Please lets continue the discussion on-list.

Superfluous, just use: https://github.com/apple/swift-nio/tree/master/Sources/NIOHTTP1


Link Visual and Collision are not exported to XML

I realized, that Visual and Collision are not exported to XML, if they are set via the Constructor.
There is also an open issue for it #42.
In addition, I realized that this issue was already fixed on the melodic-branch, see pull request #47.
Consequently, I cherry-pick the changes introduced with #47. In addition, I had to remove one test, since the Visual class does not have an attribute name anymore.
Closes: #42
Relates: #47

Can you please retarget these changes to the ros2 branch? That's where most of the development for ROS 2 happens. Once that is done, I'll do a more detailed review. Thanks!

I did not find a way to change the branch from which the changes are pulled from. (Unless opening a new PR) Thus, I repurposed the foxy-devel branch. Might not be the cleanest way, to do it ...


fix: replaced deprecated MongoDB count() with countDocuments

Pull Request Template
Summary
MongoDB count() function was deprecated, so it must be replaced with countDocuments()
Change Type
Please delete any irrelevant options.

[X ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Translation update

Testing
It is only a change of a function name
Test Configuration:
Checklist
Please delete any irrelevant options.

[X] My code adheres to this project's style guidelines
[X] I have performed a self-review of my own code
[X] My changes do not introduce new warnings
[X] Local unit tests pass with my changes

If you need a short term workaround in a running container:
sed -i 's/\.count(/\.countDocuments(/g' config/user-stats.js

thanks, cherry-picked this commit in #4951


Subaru: log stock AEB

This PR adds stock AEB dash signals logging (from #25345) and adds FCW_Cont_Beep alert to stockFcw

@sshane this good to merge?

Not quite, LKAS_Alert_Msg activates too late. Think I found the real AEB actuation bit in the ES_Brake message though

LGTM! Posted notes in the opendbc PR


[WIP] Validate XML tag names and attribute names before creating Value

If tag names and attribute names are not validated this can lead to invalid XML output.
Validation must be done in any function that create Tags, that is at least:

object
jsonToXml

Does "[WIP]" in this pull request name mean that it's not ready to be merged, or you'll finish it in another pull request?
This pull request needs the "Fix dependency to get tests running again" commit, which is included in #6: c538076ff317a2e2b52ea1df51cb1af56735b643
The new Xml.isValidXmlName needs to be included in a @docs line and it needs a documentation comment.
I could do both of these myself, but I'd prefer the pull request to be complete (and your language for the documentation comment. I simply renamed the old eeue56/elm-xml module. You've done research).

This one stands for its own and is not finished yet. Some more changes will be necessary and I'd prefer to rebase it on master after other changes are merged.
I will add docs and tests.
I'm also not yet sure how to proceed with this topic. I see two ways:

make an incompatible API change by changing object and jsonToXml to return Maybe (or Result) depending on the given tag name is valid.
don't change API but make a safe version of these functions (objectSafe, jsonToXmlSafe which return Maybe or Result). But since these object is just a helper function that is used in many places, this *Safe change would propagate to many other functions. It would lead to two versions of many functions.

I'll publish this one after you add the docs and tests.
As for proceeding after that, I think jsonToXml should change to return Maybe or Result and there should be a new objectSafe function, which returns Maybe or Result. This is because JSON values are usually received at run-time, but the tags for object are usually constant strings in the code. Forcing a multi-line change to all of those uses seems extraneous to me.
Result would be better than Maybe for both. For object it would be the bad tag name. For jsonToXml it would be either the Json.Error from JD.decodeValue or the bad tag name (as an error string or a new type with those two possibilities).

Thanks for the input. I'll continue to work on this another day.

After merging, I added an @docs line for Xml.Encode.objectSafe and an @docs line and documentation string for Xml.isValidXmlName. Then I published versions 3.1.0 and 3.1.1 (I apparently forgot to git push something for 3.1.0, hence 3.1.1; this may mean that 3.1.0 is bad).
I invited you (@schoettl) to be a contributor to the repository.

Thanks for the invitation! Alright, I thought we wait with merging this branch because I'm not sure how "finished" it was. But it shouldn't hurt anyone :)
I think I can work on it a little bit in the next few days.

Sorry for the understanding about publishing. I know you have other work to do on it. Now you should be able to publish that yourself.

No problem. I'll continue to work on this branch. I want to integrate the safe version of jsonToXml.
I'll remove the "Work In Progress" tag when I think I'm done.


svg-to-vue dependency using spread syntax which doesn't compiled

I got Uncaught SyntaxError: Unexpected token ... in some browsers, like Chrome58, is it a way to use a compatible version?

Hello, I get similar error. Looks like UglifyJs cannot parse vue-svg-loader syntax:
    ERROR in js/3.ae7f96b062b8e993ad31.js from UglifyJs
    Unexpected token: punc «(» [./node_modules/vue-svg-loader??ref--1-0!./src/svg/close.svg:4,0][js/3.ae7f96b062b8e993ad31.
js:11,14]

Hello, I have very similar problem when trying to build with Webpack 4:
    ERROR in js/40.3c2d0cc4d605b2b10d6f.js from UglifyJs
    Unexpected token: punc «(» [./node_modules/vue-svg-loader??ref--1-0!./src/svg/new/arrow-right.svg:4,0][js/40.3c2d0cc4d6
05b2b10d6f.js:11,14]

Any idea how can I fix it?

same problem

Same problem

+1

+1 😿，害我找了好久

I just fork the loader, update code manually, remove the unwanted syntax, or use another loader which I found it pass the code to vue-loader for further compile.

It can be fixed by configuring vue.config.js file correctly, I will paste my solution code later.

In vue.config.js fix like this.
const svgRule = config.module.rule('svg');
    svgRule.uses.clear();
    svgRule
      .use('babel-loader')
      .loader('babel-loader')
      .end()
      .use('vue-svg-loader')
      .loader('vue-svg-loader')
      .options({
        svgo: {
          plugins: [
            { removeDoctype: true },
            { removeComments: true },
            { removeViewBox: false }
          ],
          removeViewBox: false,
        },
      })
      .end()

Thx!
btw what does svgo mean

@GodofHope svgo is an svg optimizer.  https://github.com/svg/svgo

I thin youcanping's config should really be very prominent in the docs, so I added it to the README, see pull request https://github.com/visualfanatic/vue-svg-loader/pull/93


chore: clean up proto Value code

Update (Value) SliceBool code documentation: []bool into []typedef.Bool
Simplify string len counting in proto.Sizeof
Update switch's cases ordering to match proto Type's constants order for consistency.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (72de0f3) to head (bdc9293).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #435   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           42        42
  Lines         3669      3658   -11
=========================================
- Hits          3669      3658   -11

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Implement Teaser Carousel

As per design:

Discuss with customer the UX flow (slide to one next card, slide three next, ...)

Mobile Mock:


ng build error: Cannot find package 'destr' imported from /**/dist/.nitro/prerender/index.mjs Did you mean to import<EMAIL_ADDRESS>

Please provide the environment you discovered this bug in.
{
"name": "analog-project",
"version": "0.0.0",
"private": true,
"engines": {
"node": ">=16.0.0"
},
"scripts": {
"dev": "ng serve",
"ng": "ng",
"start": "pnpm run dev",
"build": "ng build",
"watch": "ng build --watch",
"test": "ng test"
},
"dependencies": {
"@analogjs/content": "^0.2.0-beta.7",
"@analogjs/router": "^0.2.0-beta.7",
"@angular/animations": "^16.0.0",
"@angular/common": "^16.0.0",
"@angular/compiler": "^16.0.0",
"@angular/core": "^16.0.0",
"@angular/forms": "^16.0.0",
"@angular/platform-browser": "^16.0.0",
"@angular/platform-browser-dynamic": "^16.0.0",
"@angular/platform-server": "^16.0.0",
"@angular/router": "^16.0.0",
"@nx/angular": "^16.0.0",
"front-matter": "^4.0.2",
"marked": "^4.2.12",
"prismjs": "^1.29.0",
"rxjs": "~7.5.6",
"tslib": "^2.4.0",
"zone.js": "~0.13.0"
},
"devDependencies": {
"@analogjs/platform": "^0.2.0-beta.7",
"@angular-devkit/build-angular": "^16.0.0",
"@angular/cli": "^16.0.0",
"@angular/compiler-cli": "^16.0.0",
"@nx/vite": "^16.0.0",
"nx": "^16.0.0",
"jsdom": "^20.0.0",
"typescript": "~5.0.2",
"vite": "^4.0.3",
"vitest": "^0.31.0",
"tailwindcss": "^3.3.1",
"postcss": "^8.4.21",
"autoprefixer": "^10.4.14"
}
}
Which area/package is the issue in?
Don't know / Other
Description
After create the analog project with pnpm (pnpm create analog) and after the installation, I've an error during server build using ng build.
Please provide the exception or error you saw
Building Server...
An unhandled exception occurred: Cannot find package 'destr' imported from /**/dist/.nitro/prerender/index.mjs
Did you mean to import<EMAIL_ADDRESS>
Other information
No response
I would be willing to submit a PR to fix this issue

[ ] Yes
[ ] No

It seems a problem related to pnpm.
I've had no errors in reinstalling and building the project using yarn.

Yea, there are some ongoing issues with pnpm at the moment. Try installing the destr package and adding it to your package.json in the devDependencies

Left some setup instructions here for pnpm
https://github.com/analogjs/analog/issues/361#issuecomment-1605772975


push broken - just adds a '#' to the url

I recently updated my packages, moving
    "react": "^0.14.3",
    "react-dom": "^0.14.2",
    "react-redux": "^4.0.0",
    "react-router": "^1.0.3",
    "redux": "^3.0.4",
    "redux-simple-router": "^1.0.2",
    "redux-thunk": "^0.1.0",

to
    "react": "^15.1.0",
    "react-dom": "^15.1.0",
    "react-redux": "^4.4.5",
    "react-router": "^2.4.1",
    "react-router-redux": "^4.0.4",
    "redux": "^3.5.2",
    "redux-thunk": "^2.1.0",

and now updating the url via push doesn't work. Instead, it just adds a hashtag to the url.
Any ideas what may be wrong?

Sorry - missed the piece in the docs about the routerMiddleware!


Suggestion: Add an ability to set PRNG's initial seed

Is your feature request related to a problem? Please describe.
Sometimes I need to generate the same result with the same parameter, so the fixed PRNG seed will be one of the ways to do this.
Describe the solution you'd like
Add a constructor to RandomizationBase, and implement in all Randomization class
public abstract class RandomizationBase : IRandomization
{
    protected readonly int seed;
    public RandomizationBase() : this((int)DateTime.Now.Ticks) { }
    public RandomizationBase(int seed) { this. seed = seed; }
}

I ended up creating two static methods called ResetSeed for BasicRandomization and FastRandomization, because the way that they work right now, as thread-safe, the constructor approach wouldn't work.
Bellow a sample from a unit test showing how to use the ResetSeed method:
[Test]
public void ResetSeed_GetInt_SameResults()
{
   // Resets the seed for the first time.
    FastRandomRandomization.ResetSeed(1);

    var target = new FastRandomRandomization();
    var actual = new int[10];

    for (int i = 0; i < actual.Length; i++)
    {
        actual[i] = target.GetInt(int.MinValue, int.MaxValue);
    }

   // Resets the seed again with the same value, so the pseudorandom values generated by FastRandomRandomization will follow the same order.
   FastRandomRandomization.ResetSeed(1);

    for (int i = 0; i < actual.Length; i++)
    {
        Assert.AreEqual(actual[i], target.GetInt(int.MinValue, int.MaxValue));
    }
}


Add Handlers for ISS / QAS

ISS and QAS both have Pizzabox handlers with conflicting IDs and implementations, which need to be added to this repo and ideally merged into one class which is capable of handling both.

ISS handlers: https://github.com/NSLS-II-ISS/profile_collection/blob/master/startup/10-detectors.py#L753-L839
QAS handlers: https://github.com/NSLS-II-QAS/profile_collection/blob/master/startup/11-handlers.py#L15-L112

Resolved via #3.


is Anyone run project on Local?

is Anyone running a project on Local?

Hi ravikhunt,
I just replied to your other issue thread regarding this. https://github.com/microsoft/PubSec-Info-Assistant/issues/420.


[QA] why not all examples run out of the box?

In the last three months, i have tried several examples in R or python, with a number of versions of mxnet. Very often, the examples throw errors of one kind or another when you run them 'as is'.
Do you think it would be possible to make sure all examples run before accepting a PR?
In fact, why not use the various examples as test cases where results could be checked against expected values (using fixed seeds)?
Open issues with examples problems:

#5731,"[example][rcnn][python] cv2.error","2017-04-07T18:17:26Z"
#5714,"Running error in the example code of googlenet","2017-04-06T15:56:31Z"
#5648,"Fix bugs in distributed example of TrainMnist.scala in MXNet-Scala","2017-03-31T10:50:30Z"
#5633,"Exception when using CPP package with GPU (TitanX) with mlp() example","2017-03-30T11:19:44Z"
#5621,"cpp-package lenet example throws exception","2017-03-29T21:36:08Z"
#5601,"running lazy evaluation code example outputs ""Illegal instruction""","2017-03-28T09:25:57Z"
#5596,"example/rcnn mistake--KeyError: 'width'","2017-03-28T03:06:48Z"
#5550,"example/ssd error Check failed: op != nullptr Operator MultiBoxPrior is not registered","2017-03-24T02:00:18Z"
#5480,"I have error in executing python_loss example","2017-03-19T10:17:51Z"
#5448,"Where is gen_data.py in example/bi-lstm-sort/","2017-03-17T02:47:37Z"
#5435,"issue in example warpctc/toy_ctc.py","2017-03-16T14:51:17Z"
#5431,"When I run ssd example on cpu computer, I get ""Check failed: temp.size() >= num_negative (0 vs. 3) error"" error.","2017-03-16T12:03:55Z"
#5314,"Using MKL causes C++ layer blow up while running lstm_bucketing example","2017-03-09T01:08:03Z"
#5209,"mxnet example training cannot get expected result after 0.5.0","2017-03-02T10:19:48Z"
#5201,"Missing gen_data.py in bi-lstm-sort example","2017-03-01T22:38:39Z"
#5196,"mxnet-notebook example failed.","2017-03-01T10:25:01Z"
#5149,"Fine-tune in R: end-to-end example and some troubles","2017-02-25T18:54:38Z"
#5080,"[R] image classification examples are broken","2017-02-20T22:32:36Z"
#5068,"bugs in example/numpy-ops/custom_softmax.py","2017-02-20T04:30:23Z"
#5065,"MNIST training example not exiting on CPU instances after training completion","2017-02-20T00:18:06Z"
#5052,"MXNET R, GPU speed-up much less for regression example than classification","2017-02-18T04:50:29Z"
#5047,"The example/warpctc/ocr_predict.py  has a bug,  it does not provide init_states values and run the ocr_predict.py several times and will get different results. ","2017-02-17T12:47:05Z"
#4967,"[scala-package] Running example on spark has the error java bin","2017-02-10T09:02:05Z"
#4956,"mxnet example error","2017-02-09T13:05:16Z"
#4853,"SSD example crashes on CPUs","2017-02-01T22:33:14Z"
#4826,"Alexnet and googlenet symbol in example/image-classification is wrong","2017-01-29T20:43:01Z"
#4668,"problem when running warp-ctc example on latest mxnet version","2017-01-14T03:03:47Z"
#4648,"about example error","2017-01-12T08:54:40Z"
#4640,"mxnet/example/autoencoder/mnist_sae.py not converge with the specified parameters","2017-01-11T17:52:58Z"
#4553,"CPP inference example is broken","2017-01-05T21:49:43Z"
#4540,"Get a core dump when trying to run the Scala example from the website","2017-01-05T11:03:38Z"
#4318,"Prediction fails in Handwritten Digit Recognition example","2016-12-21T08:41:51Z"
#4299,"python example/gan/dcgan.py error","2016-12-20T04:34:13Z"
#4272,"imagenet example training error","2016-12-18T00:26:54Z"
#4172,"Something wrong when I ran the example of image-classification","2016-12-09T15:10:45Z"
#4000," example/cpp/image classfication can not work in Windows","2016-11-27T04:46:32Z"
#3995,"Can't run example code with Python 3","2016-11-27T01:41:11Z"
#3965,"problem with bi-lstm-sort example ","2016-11-24T13:40:01Z"
#3948,"When I compiled mxnet with the ssd example, I got erro :","2016-11-23T08:08:15Z"
#3805,"SSD example has missing files","2016-11-12T16:51:41Z"
#3639,"multi-gpu support of joint training of rcnn example is broken","2016-10-27T10:20:15Z"
#3571,"IndentationError in the file example/fcn-xs/image_segmentaion.py line 22","2016-10-19T06:27:29Z"
#3477,"empty shapes returned in RNN example","2016-10-08T08:28:07Z"
#3315,"the bug of the adversary example","2016-09-18T02:46:17Z"
#3094,"make  memcost example error","2016-08-22T05:20:52Z"
#3061,"link in the example/kaggle-ndsb2/readme.md that describing how  to build MXNet on AWS   is invalid ","2016-08-18T10:41:30Z"
#2792,"Cannot run C++ example on Win7.","2016-07-21T08:26:14Z"
#2783,"missing script in example bi-lstm-sort","2016-07-20T12:56:05Z"
#2758,"RuntimeError when running neural-style examples","2016-07-19T03:32:40Z"
#2709,"error of ""Incorrect shape"" in example/cpp/image-classification-predict.cc  ","2016-07-15T01:50:09Z"
#2694,"MxNet/example/rcnn/demo.py  error","2016-07-14T04:10:56Z"
#2658,"MXnet Neural art example error","2016-07-09T03:54:30Z"
#2271,"example bug？","2016-05-29T03:48:19Z"
#2235,"Inception V3 model is different from the Tensorflow example","2016-05-25T08:27:53Z"
#2117,"now I run the ""example/image-classification"" with two machines,long time nothing respond ","2016-05-12T04:52:19Z"
#2048,"adversary generation example: no module named data","2016-05-06T07:01:56Z"
#1912,"why my own gray scale image can't work use train_mnisy.py as example","2016-04-20T15:39:46Z"
#1815,"fcnxs example validation accuracy does not change","2016-04-10T19:52:49Z"
#1468,"Mxnet gets stuck when run example/image-classification/train_mnist.py","2016-02-14T10:36:57Z"
#1115,"example error: typestring mismatch","2015-12-30T17:47:01Z"

One important reason seems to me that documentation is not available or out-dated.
For instance the info on C++ API on mxnet,io can be considered as obsolete. The older version of this API had at least a VS solution and a complete set of header files so you can see how to build a working sample. On the latest version of the C++ API there is no VS solution anymore so you have to find out everything by trial and error (oruse the old version and copy relevant settings).
For us, users, it is kind of free so I do not like to complain. But if there is time and/or budget for the maintainers, some more up-to-date and less cryptic documentation would at least attract more people from SME's. It is for me hard to defend it took weeks to get a bare working MxNet with C++ interface on a Win10 system with a Titan X Board .

Examples also need unit tests.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/examples/image_retraining/retrain_test.py
https://github.com/tensorflow/models/blob/master/slim/nets/inception_resnet_v2_test.py

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!

I think this issue is still alive...

Has anyone looked at example code compatibility with mxnet-mkl & Python 3.6?  I'm willing to if not.

@data4science  thanks that will be a great help!

@eric-haibin-lin sounds good.  My daily driver is MacOS, so I'm building from source.  Let me know if anyone wants the resulting build.  Then I'll go through the example code with Linux (Ubuntu 16.04, unless someone has a different distribution request).  Does it mater if the Linux run is local or on a VPS (prob. AWS).
Assuming the example code works, I'll benchmark with the provided benchmark examples.  Then I'll make a CSV file with columns for standard BLAS, MKL BLAS, & % improvement where rows are individual images.  Finally, I'll create a visualization (type determined by data).
Does this sound like a decent plan of attack?

Great of you can make time to do this effort. Personally I am interested in c++ examples getting to work. Once I finished my adjusted version of InceptionBN in C++ (changing last layers, showing how to predict images in batch without the predict interface) l will contribute this.

@Bumblebee1964 any update for the cpp examples? :)

@eric-haibin-lin Sorry I got side tracked from the MKL examples. I’ll re-focus on them.

Skipping the MacOS and going straight to VPS btw. @eric-haibin-lin should the image include gpu(s)? My thought is no since MKL is optimized for Intel CPUs. Please recommend VPS image specs for benchmarking.

Thanks @eric-haibin-lin for notifying me about https://discuss.mxnet.io/t/c-api-batch-mode/253/1 I will answer this thread later this week.
I have not yet figured out how to publish a sample on github and last weeks busy figuring out how to compile mxnet 0.11 with cpp-package and GPU support, which I recently accomplished.


restorePreviousWindowsOnStart works only when path is not specified

By request of @50Wliu, I'm opening a new issue to complement the closed #6605.
restorePreviousWindowsOnStart seems to work only when atom is launched without a specified location, as reported by @andreaferretti. See also https://discuss.atom.io/t/remember-open-projects-when-reopening-atom/7053/37

I don't know whether it is the same issue of mine: when installed some update of packages, I click the restart button on the popup, then the previous state of window changed. I opened 2 or 3 projects in one maximized window with separated tabs. after restart, the previous tabs in one window changed to separated windows.
Mac OS


kubefirst: 2.4.9 -> 2.4.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/kubefirst/versions.
meta.description for kubefirst is: Tool to create instant GitOps platforms that integrate some of the best tools in cloud native from scratch
meta.homepage for kubefirst is: https://github.com/kubefirst/kubefirst/
meta.changelog for kubefirst is: https://github.com/kubefirst/kubefirst/releases/tag/v2.4.10
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.4.10 with grep in /nix/store/575xfcpvh9sypjaxr216wh150aq9kd2d-kubefirst-2.4.10
found 2.4.10 in filename of file in /nix/store/575xfcpvh9sypjaxr216wh150aq9kd2d-kubefirst-2.4.10

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

kubefirst

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/575xfcpvh9sypjaxr216wh150aq9kd2d-kubefirst-2.4.10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kubefirst https://github.com/r-ryantm/nixpkgs/archive/b87a5f8a15ef07c50ad873ca148189f1ef0e5654.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b87a5f8a15ef07c50ad873ca148189f1ef0e5654#kubefirst

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/575xfcpvh9sypjaxr216wh150aq9kd2d-kubefirst-2.4.10
ls -la /nix/store/575xfcpvh9sypjaxr216wh150aq9kd2d-kubefirst-2.4.10/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

kubefirst

Maintainer pings
cc @qjoly for testing.

@QJoly Shell completion is missing.


use memref for the array sierra type instead

it may lead to better optimizations since its higher level
todo: check how feasible this is

We checked when refactoring to the actual project. It is not possible because the memref type can't have an LLVM struct as its element type, that is: memref<!llvm.struct<()>> is invalid.


SG-255IE Breaker Spray&Pray is missing it's "y"

https://github.com/helldivers-2/json/blob/e57d9c4b7a4c770853a34fa341017acc8e3b48ce/items/weapons/primary.json#L135

Addressed by #24


Introduce gardener-operator and Garden CRD

How to categorize this PR?

/area dev-productivity delivery
/kind enhancement
What this PR does / why we need it:
This PR introduces the new gardener-operator component which will reconcile the Garden CRD for bringing up "garden system components" and "virtual garden control plane components" like

gardener-resource-manager for bringing enterprise-grade qualities to the garden cluster (token invalidation, seccomp defaulting, HA config, etc.)
etcd-druid for bringing up the ETCD + backup-restore (cluster) for the virtual garden
kube-apiserver and kube-controller-manager for the virtual garden
vertical-pod-autoscaler and hvpa-controller
Gardener control plane
Observability stacks
...

This PR only handles the GRM and the VPA deployment.
The backing motivation is: As of today, operators have to manually deploy the "garden system components" and the "virtual garden control plane components". However, logically these processes is quite similar to what we already do for seed or shoot clusters. Hence, this gardener-operator re-uses existing code and shares it with gardenlet so that the needed components can be made available more easily in all environments.
Related PR: https://github.com/gardener/ci-infra/pull/489
Release note:

There is a new `gardener-operator` component responsible for reconciling the new `Garden` CRD. Read more about it [here](https://github.com/gardener/gardener/blob/master/docs/concepts/operator.md).

/test pull-gardener-integration

/assign

/assign

Thanks colleagues, I will address your feedback tomorrow morning.
@timebertt, it would be great to get yours as well by tomorrow so that we can proceed with this story :)

/test pull-gardener-e2e-kind-ha-single-zone

/lgtm

/lgtm

Thanks for all your reviews folks! I'm very excited about this one, let's go :)
/unhold


Trying to make 0.100 buildable

Nudging xorcery-example to be compatible with Xorcery 0.100.X release

@StigLau I appreciate that you are interested in this and want to get it to work. However, you don't know what I'm working on, or what the roadmap is, so the effort is a bit wasted and the timing is off. Let's connect (ping me on rickardoberg@gmail.com), and I'll tell you what's coming up, and when it makes sense to fix the examples.
The goal of Xorcery from the beginning has been to create an evolvable architecture, meaning where you can start with a simple monolith and evolve it step by step into a fully scalable microservices app without changing the building blocks. I'm almost there, but not just yet. Let's sync, and you'll have a less frustrating time :)


Updating Espresso XCUITest docs to ref saucectl

Description
Edited docs under /mobile-apps/automated-testing/espresso-xcuitest to remove refs to Sauce Runner and instead ref saucectl. Also added a migration map for Test Object users to compare old commands with saucectl equivalents.
Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[ ] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Thanks for all your help, @FriggaHel! I think I have addressed all of your comments, so if you wouldn't mind taking a final look! Thanks!


I can not reach the url to download the weights.

I can not reach this url:
sceneparsing.csail.mit.edu/model/pytorch

@SharifElfouly Hi, our server is under maintenance today, it will come back tomorrow. Sorry about that.


Long running resolve due to backtracking

With PEX 2.1.92 on both Linux and macOS, the following lockfile generation seemingly runs indefinitely:
pex3 lock create -vvvvvvvvv --output=lock.json --no-emit-warnings --style=universal --resolver-version pip-2020-resolver --indent=2 --no-pypi --index=https://pypi.org/simple/ --interpreter-constraint 'CPython==3.8.*' 'Cython' 'Flask' 'Jinja2' 'Pillow' 'PyJWT==2.3.0' 'PyQt5' 'SQLAlchemy' 'alembic' 'cachetools' 'cbor2' 'cffi' 'cirq-core' 'ciso8601' 'click' 'coverage' 'cryptography>=3.3.1' 'dash' 'deepdiff' 'dill' 'elasticsearch' 'email-validator>=1.0.3' 'fastapi-pagination==0.9.3' 'fastapi-utils==0.2.1' 'fastapi==0.65.2' 'fire' 'flaky' 'frepr' 'gitpython' 'gunicorn' 'humanize' 'influxdb-client' 'influxdb-client[ciso]' 'ipython' 'logstash-formatter' 'matplotlib<4,>=3.0.3' 'minio==4.0.21' 'mocker==1.1.1' 'mongomock' 'numpy==1.18.5' 'opsgenie-sdk' 'ortools' 'oso>=0.26.1' 'packaging>=20.9' 'pandas' 'pantsbuild.pants.testutil<2.12,>=2.11.0rc0' 'pantsbuild.pants<2.12,>=2.11.0rc0' 'protobuf' 'psutil' 'psycopg2-binary' 'pydantic<2,>=1.8.2' 'pygit2==1.1' 'pymongo' 'pyqtgraph' 'pyserial' 'pytest-mock' 'pytest-qt' 'python-dateutil' 'pytz' 'pyzmq' 'qiskit' 'requests' 'rich' 'rtoml' 'schedule' 'scikit-learn' 'scikit-optimize' 'scipy' 'sendgrid' 'simple-pid' 'simplejson' 'sqlalchemy-oso>=0.26.0' 'tenacity' 'testbook' 'typer' 'types-Flask' 'types-cachetools' 'types-certifi' 'types-protobuf' 'types-psycopg2' 'types-python-dateutil' 'types-pytz' 'types-requests' 'types-simplejson' 'types-six' 'types-toml' 'typing_extensions' 'tzdata' 'tzlocal' 'urllib3' 'uuid' 'uvicorn' 'werkzeug' 'zhinst==20.7.2701' 'zstandard'

Inspecting top shows that the time is in a pip process, whose log has a series of lines like:
2022-06-01T12:06:26,197 INFO: pip is looking at multiple versions of pydantic to determine which version is compatible with other requirements. This could take a while.
2022-06-01T12:07:38,584 INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. If you want to abort this run, you can press Ctrl + C to do so. To improve how pip performs, tell us what happened here: https://pip.pypa.io/surveys/backtracking
2022-06-01T12:10:51,680 INFO: pip is looking at multiple versions of pillow to determine which version is compatible with other requirements. This could take a while.
2022-06-01T12:15:29,097 INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. If you want to abort this run, you can press Ctrl + C to do so. To improve how pip performs, tell us what happened here: https://pip.pypa.io/surveys/backtracking

I've got a log tailer with filters hacked up for this. Tracking in #1801 and closing this issue as (self) answered @stuhood.


You can try running the following commands to get more insight on what is happening:
Do not copy paste since you will go from bash to torch interpreter!
# start lua in a debugger
gdb luajit
# wait for gdb to start
# start luajit
r
# you should now see the luajit command prompt
# run the code that cause the segfault
require 'torch'
require 'cutorch'
# this should crash and get you back to gdb
# print the backtrace
bt
# send us this backtrace.

I sloved it ,because someone else is using the gpu when I running the codes.The ram is not enough so  Segmentation fault came.Anyway,thank you guys so much!!!

Hi,
i encounter with the same error and i run command of aldben:

gdb luajit
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from luajit...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/luajit
LuaJIT 2.0.4 -- Copyright (C) 2005-2015 Mike Pall. http://luajit.org/
JIT: ON CMOV SSE2 SSE3 SSE4.1 fold cse dce fwd dse narrow loop abc sink fuse

require 'torch'
error loading module 'libpaths' from file '/home/atefe/torch/install/lib/lua/5.2/libpaths.so':
/home/atefe/torch/install/lib/lua/5.2/libpaths.so: undefined symbol: luaL_setfuncs
stack traceback:
[C]: at 0x004525b0
[C]: in function 'require'
/home/atefe/torch/install/share/lua/5.2/paths/init.lua:1: in main chunk
[C]: in function 'require'
/home/atefe/torch/install/share/lua/5.2/torch/init.lua:12: in main chunk
[C]: in function 'require'
stdin:1: in main chunk
[C]: at 0x004044a0


Using MDG Camera package in Electron Desktop

Hi,
I am using MDG Camera package which allows you to take a picture on any device you are on.
But this package is not included in the desktop build. Below is the package.js
The lines below show that the css and js is added to web.browser.
api.addFiles("camera.less", ["web.browser"]);
api.addFiles('photo-browser.js', ['web.browser']);

But we need these added to the desktop as well. But the exported variable MeteorCamera exported by api.export('MeteorCamera'); is not defined.
Below is the whole package.js for mdg:camera. Let me know how I can have this added to the desktop build.
Package.describe({
  name: "mdg:camera",
  summary: "Photos with one function call on desktop and mobile.",
  version: "1.4.1",
  git: "https://github.com/meteor/mobile-packages"
});

Cordova.depends({
  "cordova-plugin-camera": "2.3.1"
});

Package.onUse(function(api) {
  api.export('MeteorCamera');
  api.use(["templating", "session", "ui", "blaze"<EMAIL_ADDRESS>"reactive-var"]);
  api.versionsFrom("METEOR@1.2");
  api.use("isobuild:cordova@5.2.0");

  api.addFiles('photo.html');
  api.addFiles('photo.js');
  api.addFiles("camera.less", ["web.browser"]);
  api.addFiles('photo-browser.js', ['web.browser']);
  api.addFiles('photo-cordova.js', ['web.cordova']);
});

UPDATE:
Actually MeteorCamera is defined but the package fails because navigator.camera.getPicture  is not defined which MeteorCamera uses.

UPDATE:
Ohh, actually, what is happening is that the MDG:Camera package is trying to use the cordova method for getting a picture instead of the browser method, since we are grabbing the cordova build.
Ah so basically we need to add api.addFiles('photo-browser.js', ['web.browser']); to the desktop platform

Yes, you are right. Its including the cordova files. This is unfortunately a drawback when it comes to the way meteor-desktop is implemented and without hacking there is not much I can do about it.
I do not like it when I need to suggest a workaround but in this case you will have to make a fork of that package and do some changes.
If you do not need it working on cordova just change web.browser to client in package.js
If you do need cordova,  then do the same as above but remove photo-cordova.js and add its contents to photo-browser wrapping the definition of MeteorCamera.getPicture into an if.
if (!Meteor.isCordova) {
 MeteorCamera.getPicture // from photo-browser.js
} else {
 MeteorCamera.getPicture // from photo-cordova.js
}

Have you manage to work it out?

Oh yah was easy, just had to extract the photo-browser.js code and use that on the desktop side.


Check Max buffer size in libp2p; could mean we're dropping stdin/stdout messages

Figure out the max and verify that we are not hitting it.  Check with @deepthiskumar  may have information about current size?

It is currently 1GB
https://github.com/MinaProtocol/mina/blob/ecc4afbad2ab8ec3d85c4e9eaaa3c2762cd3f6b6/src/app/libp2p_helper/src/libp2p_helper/main.go#L1103


What happens when a Key Vault-Managed Storage Account resource ID changes?

What happens when I move my Key Vault-managed storage account to a different resource group? Then the resource ID of the storage account changes. Does this break Key Vault?
It would be good to add a note about this.

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

ID: cebec73e-e7f4-75c5-2068-ae89f12d8d95
Version Independent ID: e2497a7b-3b5f-554a-1a31-da540740fcc9
Content: Azure Key Vault Storage Account Keys
Content Source: articles/key-vault/key-vault-ovw-storage-keys.md
Service: key-vault
GitHub Login: @lleonard-msft
Microsoft Alias: alleonar

@smflorentino The resourceId does not change and it does not break when the key-vault is moved from one resource group to another resource group.

The resource ID does change, since the resource ID contains the resource group name.
Can you confirm that a changing resource ID does not break the KeyVault management?

@smflorentino my bad, I have checked the SubscriptionId of the Key-Vault and yes, you are correct it does change.  Moving across the different resource groups won't break the key-vault if it is in the same subscription, however, there are certain exceptions like VM using key-vault with certificate stored can be moved to a new resource group in the same subscription, but not across subscriptions. You can refer to these links:

Change a key vault tenant ID after a subscription move
Move resources to new resource group or subscription

@smflorentino We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


theme: fix Safari bug for auto-column-grid

Closes https://github.com/inveniosoftware/demo-inveniordm/issues/122

Adds max-width to second child in .auto-column-grid, to fix excess spacing bug in Safari.

Video recording

we should move the whole class to invenio-theme because we are using it in invenio-administration (check the screenshot), so it should be global

we should move the whole class to invenio-theme because we are using it in invenio-administration (check the screenshot), so it should be global

Ok, I see! Will move it! :)

Update
Removed auto-column-grid class, added to invenio-theme https://github.com/inveniosoftware/invenio-theme/pull/347


types / TypeScript?

hey there 👋
tl;dr i'd REALLY like to use this in my tests but i'm balking at the prospect of not having types. any plans to move this plugin to typescript? or provide a @types/ package?
thanks for your time
kayak

That's a good point, I'll take a look into that over the next few days.


scrape target not honoring https scheme

Bug Report
What did you do?
Attempt to scrape a Kubernetes API endpoint using scheme https and a bearer_token.
What did you expect to see?
A successful scrape over https, like https://<api_endpoint_ip_address>:443/..., not http://<api_endpoint_ip_address>:443/...
What did you see instead? Under which circumstances?
A scrape error for the airflow-metrics target, while the federated_prometheus target has no problems.
Get http://<api_endpoint_ip_address>:443/api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics/: net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x15\x03\x01\x00\x02\x02"

curl commands to validate the issue
Works:
curl -k https://<api_endpoint_ip_address>:443/api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics/ -H "Authorization: Bearer ${TOKEN}"

Doesn't Work:
$ curl -k http://<api_endpoint_ip_address>:443/api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics/ -H "Authorization: Bearer ${TOKEN}"

curl: (56) Recv failure: Connection reset by peer

Environment

System information:
for local testing Darwin 17.7.0 x86_64
usually I'm running prometheus in a GKE cluster running node and master versions 1.11.5

Scrape Target GKE master version:
airflow cluster: 1.9.7
federated GKE cluster: 1.11.5

Prometheus version:
v2.4.0 on the GKE cluster
v2.6.1 locally

Prometheus configuration file:
This is a sample configuration that I'm running locally that shows the 2 different scrape targets with similar configurations. The same error is seen both locally and in GKE.

global:
  scrape_interval: 30s
  scrape_timeout: 10s
  evaluation_interval: 30s
scrape_configs:
- job_name: airflow-metrics
  honor_labels: true
  metrics_path: /api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics
  scheme: https
  params:
    match[]:
      - '{__name__=~"airflow.*"}'
  static_configs:
  - targets:
    - <api_endpoint_ip_address>
  bearer_token: <blah>
  tls_config:
    insecure_tls_verify: true
- job_name: federated_prometheus
  honor_labels: true
  static_configs:
    - targets:
      - <gke_api_endpoint_ip>
  scrape_interval: 60s
  scrape_timeout: 60s
  params:
    match[]:
      - '{namespace="default"}'
  metrics_path: /api/v1/namespaces/default/services/prometheus:9090/proxy/federate
  scheme: https
  bearer_token: <blah>
  tls_config:
    insecure_skip_verify: true

Logs:

12:06 $ prometheus --log.level=debug
level=info ts=2019-01-17T17:06:50.679835Z caller=main.go:243 msg="Starting Prometheus" version="(version=2.6.1, branch=non-git, revision=non-git)"
level=info ts=2019-01-17T17:06:50.68023Z caller=main.go:244 build_context="(go=go1.11.4<EMAIL_ADDRESS>date=20190116-23:28:29)"
level=info ts=2019-01-17T17:06:50.680255Z caller=main.go:245 host_details=(darwin)
level=info ts=2019-01-17T17:06:50.680276Z caller=main.go:246 fd_limits="(soft=256, hard=unlimited)"
level=info ts=2019-01-17T17:06:50.680294Z caller=main.go:247 vm_limits="(soft=unlimited, hard=unlimited)"
level=info ts=2019-01-17T17:06:50.680886Z caller=main.go:561 msg="Starting TSDB ..."
level=info ts=2019-01-17T17:06:50.681758Z caller=web.go:429 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090
level=info ts=2019-01-17T17:06:51.003115Z caller=main.go:571 msg="TSDB started"
level=info ts=2019-01-17T17:06:51.003168Z caller=main.go:631 msg="Loading configuration file" filename=prometheus.yml
level=debug ts=2019-01-17T17:06:51.00729Z caller=manager.go:213 component="discovery manager scrape" msg="Starting provider" provider=string/0 subs=[airflow-metrics]
level=debug ts=2019-01-17T17:06:51.00772Z caller=manager.go:213 component="discovery manager scrape" msg="Starting provider" provider=string/1 subs=[federated_prometheus]
level=info ts=2019-01-17T17:06:51.007758Z caller=main.go:657 msg="Completed loading of configuration file" filename=prometheus.yml
level=info ts=2019-01-17T17:06:51.007773Z caller=main.go:530 msg="Server is ready to receive web requests."
level=debug ts=2019-01-17T17:06:51.007784Z caller=manager.go:231 component="discovery manager scrape" msg="discoverer channel closed" provider=string/0
level=debug ts=2019-01-17T17:06:51.007835Z caller=manager.go:231 component="discovery manager scrape" msg="discoverer channel closed" provider=string/1
level=debug ts=2019-01-17T17:07:06.926837Z caller=scrape.go:825 component="scrape manager" scrape_pool=airflow-metrics target="https://<api_endpoint_ip_address>:443/api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics?match%5B%5D=%7B__name__%3D~%22airflow.%2A%22%7D" msg="Scrape failed" err="Get http://<api_endpoint_ip_address>:443/api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics/?match%5B%5D=%7B__name__%3D~%22airflow.%2A%22%7D: net/http: HTTP/1.x transport connection broken: malformed HTTP response \"\\x15\\x03\\x01\\x00\\x02\\x02\""
^Clevel=warn ts=2019-01-17T17:07:16.21424Z caller=main.go:405 msg="Received SIGTERM, exiting gracefully..."

I agree to put this on the list for Prometheus 3.0.

Hmm, could we handle the redirect better? There's basically the same issue over in the blackbox exporter too.

What do you mean?
A HTTPS target that redirects to HTTP might be valid.

It'd valid, but inefficient. We should scrape the required target directly.

any followup on this?
we have no redirects in place,
configuration is aiming to https
... nevertheless the instance is calling http instead of https

reproducible in 2.10.... i'm going to check where got introduced... we just upgrade from 2.4.3

ok, my issue was slightly different... we had an endpoint with no https:// or http:// for the api_server ... and somehow schema: https was not respected in the composition of the URL

According to the documentation it's supposed to be scheme: https instead of schema: https

While I think there is still a problem, I believe that I have resolved the immediate issue. The metrics_path that I was using caused a 301 to be returned from the target, specifically needing to add a trailing / to the path. Because the scrape target is actually the kubernetes API endpoint, not the service itself, the 301 from the service came back as an http:// redirect. Here's the verbose curl output
$ curl -v -k https://<api_endpoint_ip_address>:443/api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics -H "Authorization: Bearer $TOKEN"
*   Trying <api_endpoint_ip_address>...
* TCP_NODELAY set
* Connected to <api_endpoint_ip_address> (<api_endpoint_ip_address>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Request CERT (13):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=<api_endpoint_ip_address>
*  start date: Sep 18 12:37:35 2018 GMT
*  expire date: Sep 17 12:37:35 2023 GMT
*  issuer: CN=1d0c9ada-8bf7-408b-92fb-a4f715e32eb5
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fee73800400)
> GET /api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics HTTP/2
> Host: <api_endpoint_ip_address>
> User-Agent: curl/7.54.0
> Accept: */*
> Authorization: Bearer  blahblahblah
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 301
< audit-id: b8d54cfb-8290-405f-86a4-fd33884e5f7d
< content-type: text/html; charset=utf-8
< date: Fri, 18 Jan 2019 18:45:38 GMT
< location: http://<api_endpoint_ip_address>/api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics/
< server: gunicorn/19.9.0
< content-length: 279
<
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>Redirecting...</title>

Redirecting...

* Connection #0 to host <api_endpoint_ip_address> left intact

You should be redirected automatically to target URL: <a href="http://<api_endpoint_ip_address>/admin/metrics/">http://<api_endpoint_ip_address>/admin/metrics/.  If not click the link.

So this explains why if I have a scrape config with
metrics_path: /api/v1/namespaces/default/services/<service>:8080/proxy/admin/metrics/

I don't get the malformed 301 and all of a sudden I have a working endpoint.
I guess this just turns into a "please generate greater debug logging" request.

Thank you I beat my head on this same problem for the better part of 3 hours.

We can close this issue after #8546 got merged.

Hello from the bug scrub.
Closing this as per the previous comment. Please follow up if that's a mistake.


Question about implementing littlefs port for nor spi flash

Should the port's prog and erase functions wait until those operations are complete on the SPI flash before the function returns or can the function return while the operation is still in progress? Said another way should the prog and erase functions verify (either wait the appropriate time or better yet poll the flash chip) for operation completion before returning?
When does littlefs call sync? Will sync always be called in between a prog (or erase) and a read? Can littlefs call multiple progs back to back without calling sync in between?
I'm looking for best practices on where operation verification needs to be placed. Thanks!

Hi @Houe2005, interesting question.
The sync callback marks the point in time where littlefs needs pending write operations to be reflected on disk. The reason for sync is to allow the hardware to best take advantage of buffers and caching that is available.
So it should be fine to delay progs and erases until sync. littlefs will make sure to call sync before reading from the page (though it may read from other pages while building the commit, line 1311 for example).

Said another way should the prog and erase functions verify (either wait the appropriate time or better yet poll the flash chip) for operation completion before returning

You only need to poll in sync.
Though it's worth noting that polling during prog/erase may be easier to implement. So unless you're writing large files or go a while without calling lfs_file_close/sync, it may not be worth the extra logic to delay a poll until sync.

Will sync always be called in between a prog (or erase) and a read?

Yep!

Can littlefs call multiple progs back to back without calling sync in between?

Yes, littlefs may call erase/prog any number of times before calling sync. If you write a file, littlefs will erase+prog enough blocks to store the file data and the file's metadata, only calling sync when you close/sync the file.
Hopefully that helps answer some questions.

Thanks for the reply geky it was very helpful.


⚠ Bofrost.com has degraded performance

In 6dc74cd, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 541 ms

Resolved: Bofrost.com performance has improved in b98161d after 6 minutes.


langchain-community[patch]: unstructured loader support extractImageBlockType option

Fixes #5942

Thank you very much!


1.1-1.2X faster rendering by avoiding unncessary shadow shader calls

Below is my commit:
https://github.com/ElaraFX/OpenShadingLanguage/commit/d319ae6175ad4dd7d6b53d2f44aa1f5f793412fa
But my codebase is very old... Too time consuming to solve conflicts... I think it's better to share the idea here.

This looks really interesting. I can turn this patch into a PR for you, but I still really need a CLA from you guys before I'm allowed to merge it.

This optimization is only valid for renderers that only look at the transparent closure on shadow rays.
I think its better for renderers to implement this optimization themselves because they are the only ones that know what the different closures mean with respect to their raytypes.
A related optimization we've talked about in the past but never implemented was do provide a way for renderers to advertise the list of closures they will be looking for (for example, for shadow ray shaders it could be just the "transparent" closure in many cases). Then the optimizer would be free to turn any other closure calls it finds into no-ops, thus triggering extra optimizations. In that case the shader writer might not even need to litter their code with raytype() queries at all.

I totally agree with @fpsunflower
What he's suggesting is what we're trying to do next... We found a large potential by doing this because we can turn constant transparent shader into a cached opacity value. this would be a huge optimization for scenes with many glass materials.
@lgritz Please mail CLA to me. My mail address is<EMAIL_ADDRESS>(I remember I signed CLA for OpenImageIO already...)

Individual CLA
Corporate CLA.

Scanned, signed CLAs can be emailed to<EMAIL_ADDRESS>

@lgritz Sent the CLAs.

Did you? To that address mentioned above? I didn't see it. Can you try again? Or directly to me: lg AT imageworks.com?

@lgritz Sent again to both opensource and lg AT imageworks.com
Still not working?

Yes, got it this time.
I think you've changed userids or emails over the years, I didn't realize you had already send in a CLA.

As far as this issue, I think we are all in agreement here that your patch -- while a good idea -- has the potential to break other renderers, and in the long term we should be aiming for the more general solution (where renderers communicate the set of closures interesting to them for each ray type, rather than those associations being hard-coded as in your original patch).

@lgritz No problem. Looking forward to the general solution. So I'm closing this one.


Release optimized PLONK verifier

Description:
For the details you can refer to the main PR with changes: https://github.com/matter-labs/era-contracts/pull/16.
Audit:
External

Blocked by #37 ?

@vladbochok no, this one goes into main and so should be merged roughly at the same time as we will start integrating it into the testnet/mainnet (i.e. the old proof system), while #37 is for boojum

Though actually since #37 supports both aggregation and lack of it, it is indeed better to wait for it to be finalized and then use it here also

The optimized PLONK verified has been released as part of boojum release


Recommendation 42: NASA should develop a comprehensive software preservation and archiving strategy that ensures discoverable, accessible, and usable software tools....

Recommendation 42
NASA should develop a comprehensive software preservation and
archiving strategy that ensures discoverable, accessible, and usable software tools. The
curation of the collection of NASA-funded software products through a designed software
node within PDS, a centrally managed catalog, or with another approach will ensure the
successful implementation of NASA open-source software policies.

PDS Management Response:

The PDS Engineering node has an on-line tool registry listing of relevant software products.  https://pds-gamma.jpl.nasa.gov/tools/tool-registry/.
PDS nodes websites list their respective tools.


nesting rows inside expanded row

How to reproduce this bug:

Step one
create a div with class 'row expanded'

Step two
nest a div with class 'row' inside and then another div with class 'row' inside of that one.

Step three
observe that content doesn't align.

What should happen:
users should have ability to expand rows nested inside of expanded rows to full width of previous row.
What happened instead:
padding compounds and rows nested inside an expanded row don't align.
Test case:
-Click here for CodePen illustrating the issue

You can use .collapse on rows to get rid of that padding 😄
codepen
collapse docs

you can use row instead of column in your code to get rid of space

Expanded Row

nested row

second nested row

@satyajit11 You get the same result if you just delete the .columns divs that you changed, so changing them to .row is redundant. It also results in the same problem with using collapse; you lose your outer padding in the nested expanded rows.

try this it will fix padding issue
codepen

Expanded Row

nested row

nested expanded row

@satyajit11 That looks like a different use case. He wants to nest expanded rows in a contained row in an expanded row but, if you do so, the outer padding isn't applied to the nested expanded rows.
In your example, which is correct albeit for a different use case, all of the nested rows are expanded to full width.

Looks like an answer was provided for this. Closing.


Remove async from DrandBeacon construction

Summary of changes

Changes introduced in this pull request:

removed async from DrandBeacon construction - a blocking check should be acceptable there given that it's only for debugging,
removed unnecessary async that resulted from the above,
revived one test (though I had to disable height check because of a missing stateroot, it's probably because of our lack of support for older network versions for now)

Reference issue to close (if applicable)

Closes https://github.com/ChainSafe/forest/issues/2408
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Sorry I didn't spot this earlier but could you make MessagePool::new be non-async as well? It just needs to have the async keyword removed.

Sorry I didn't spot this earlier but could you make MessagePool::new be non-async as well? It just needs to have the async keyword removed.

of course

state_setup is also no longer async, I believe.

Indeed, I expected clippy to find this, but I guess my expectations were too high.


Datalist component

Summary
Implement an HTML datalist element as an Angular control, and make sure it fits well within our forms layouts and styling.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/datalist

What is the change? This is a new component but of an existing HTML element that is widely supported
Why should it go in Clarity? It provides a limited combobox like behavior and might be ideal in many scenarios
Does this change impact existing behaviors? If so how? No its new
If this change introduces a new behavior, is this behavior accessible? It should be the same as other form controls

Use case
We've seen people using dropdowns to create a combobox like functionality, but a datalist is often sufficient.
Examples
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/datalist
Workarounds
Is there a workaround for this feature at the moment, even if it is less than ideal?

I would like to be assigned. Thanks!

Im currently working on this. I investigated the datalist more carefully and i found that css style wont work for these datalist options.

In this case, what should be done?

For this, the best styling that we can do out of the box is where we should start. We don't style everything in a select box fully because HTML form elements don't always have ways to do this. So get as far as possible and we'll review it.