text:
[SPARK-42894][CONNECT] Support cache/persist/unpersist/storageLevel for Spark connect jvm client

What changes were proposed in this pull request?
This pr follow SPARK-42889 to support cache/persist/unpersist/storageLevel for Spark connect jvm client
Why are the changes needed?
Add Spark connect jvm client api coverage.
Does this PR introduce any user-facing change?
No
How was this patch tested?

Add new test

cc @HyukjinKwon @hvanhovell FYI

Merged to master/3.4.
Thank you, @LuciferYang and @HyukjinKwon .

Thanks @dongjoon-hyun @HyukjinKwon

authors: LuciferYang dongjoon-hyun


text:
[SPARK-44873][3.4] Support alter view with nested columns in Hive client

What changes were proposed in this pull request?
Backport https://github.com/apache/spark/pull/42532

Why are the changes needed?
Support CREATE and ALTER VIEW with Hive-incompatible schema

Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit tests

Sorry, but this looks like an improvement instead of bugs. IIUC, Apache Spark has never support this before, doesn't it?

@dongjoon-hyun FYI I don't have a strong opinion on this one.  If you are against it, I will not merge it.

Thank you, @gengliangwang . Apache Spark 3.5.0 looks enough for me. Since this is merged to Spark 3.5.0, the users can use this with 3.5.0 if they really want.

Yeah, let's probably don't backport to 3.4 although it's sort of safe.

Thank you, @HyukjinKwon , too.

Let me close this backport PR. Thank you all.

source: gharchive/pull-request

authors: HyukjinKwon dongjoon-hyun gengliangwang kylerong-db

repo: apache/spark

license_type: permissive

license_source: github-api


text:
[MINOR][PYTHON][TESTS] Add init file to pyspark.ml.tests.connect

What changes were proposed in this pull request?
This PR proposes to add __init__.py file to pyspark.ml.tests.connect
Why are the changes needed?
To make pyspark.ml.tests.connect as a canonical Python package
Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A
Was this patch authored or co-authored using generative AI tooling?
No.

I manually tested this.
Merged to master.


text:
[SPARK-45685][CORE][SQL] Use LazyList instead of Stream

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Was this patch authored or co-authored using generative AI tooling?

Test first, will update pr description later

Thanks @dongjoon-hyun

@JoshRosen I have submitted a pr: https://github.com/apache/spark/pull/46970, please let me know if I have correctly understood your suggestion.
If current pr has a significant impact on performance, we can also revert it.

I think that this PR may have introduced a rare performance / StackOverflowError regression:

I would like to understand more, is this issue due to the design of LazyList itself? Should we submit an issue to the Scala community?


text:
[WIP][SPARK-47234][BUILD] Upgrade Scala to 2.13.13

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Was this patch authored or co-authored using generative AI tooling?

From GA testing, it seems that ammonite has not yet supported scala 2.13.13.
com.lihaoyi:ammonite_2.13.13:2.5.11

Thank you, @panbingkun !

Actually, according to the release note, we need to upgrade SBT too.

Users of sbt must upgrade to sbt 1.9.9 to use the console task to access the 2.13.13 REPL (sbt/sbt#7502); error message is NoSuchMethodError: org.jline.utils.AttributedString.fromAnsi

I also saw your SBT 1.9.9 test PR and its failure.

[WIP][Only Test] Test sbt 1.9.9 #45345

In the worst case, we cannot upgrade to Scala 2.13.13.

Yes, but unfortunately, from the test results of another PR, it seems that sbt 1.9.9 still has issues starting from version sbt 1.9.4. (When there is a corrupted jar in Maven's local repo, it will fail)

Yes, that's what I meant exactly. Scala 2.13.13 requires SBT 1.9.9 but SBT 1.9.9 is not working properly. In short, there is no working combination in Scala 2.13.13 and this is the worst case where we are currently standing. I don't know if SBT 1.9.10 might solve every issues, but it's also unlikely.

Yes, but unfortunately, from the test results of another PR, it seems that sbt 1.9.9 still has issues starting from version sbt 1.9.4. (When there is a corrupted jar in Maven's local repo, it will fail)

Yes, that's what I meant exactly. Scala 2.13.13 requires SBT 1.9.9 but SBT 1.9.9 is not working properly. In short, there is no working combination in Scala 2.13.13 and this is the worst case where we are currently standing. I don't know if SBT 1.9.10 might solve every issues, but it's also unlikely.

Yes, but unfortunately, from the test results of another PR, it seems that sbt 1.9.9 still has issues starting from version sbt 1.9.4. (When there is a corrupted jar in Maven's local repo, it will fail)

I have already submitted a bug report to SBT: https://github.com/sbt/sbt/issues/7506
But it seems to be a problem with the coursier .

From GA testing, it seems that ammonite has not yet supported scala 2.13.13. com.lihaoyi:ammonite_2.13.13:2.5.11
A PR has been submitted to the upstream ammonite community to address this issue: com-lihaoyi/Ammonite#1430

In fact, https://github.com/com-lihaoyi/Ammonite/pull/1421 is already in the process of upgrading, there are probably some tests that have not passed yet

It seems that 3.0.0-M1 is released last week.
Could you rebase the PR? I guess the only remaining issue is SBT?

It seems that 3.0.0-M1 is released last week.
Could you rebase the PR? I guess the only remaining issue is SBT?

Okay, let me try it.

If CI passed, shall we land this to master first to investigate SBT issues further, @panbingkun and @LuciferYang ? It would be must faster to find any potential issues if this patch is in master branch because all people and Daily CIs will verify this.

authors: LuciferYang dongjoon-hyun panbingkun


text:
[SPARK-6396][Core] Add broadcast timeout

TorrentBroadcast uses fetchBlockSync method of BlockTransferService.scala which wait Duration.Inf. A timeout would be better.

Can one of the admins verify this patch?

Maybe we should document the new configuration in configuration.md.

Hi @chidouhu could you update the patch to address the comments?

ok, i'll update soon.
2015-06-19 9:30 GMT+08:00 andrewor14 notifications@github.com:

Hi @chidouhu https://github.com/chidouhu could you update the patch to
address the comments?
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/5197#issuecomment-113336143.

Can one of the admins verify this patch?

I think that we should revisit this for 1.5, since this looks like an application-level way to address the issues raised in #7653.

ok to test.
@chidouhu would you mind addressing the comments so we can proceed with this patch?

This PR is largely out of date by now. @chidouhu would you mind closing this for now? We can always re-open later if there's interest.

ok, i'll close it, thx.
2015-10-17 4:58 GMT+08:00 andrewor14 notifications@github.com:

This PR is largely out of date by now. @chidouhu
https://github.com/chidouhu would you mind closing this for now? We can
always re-open later if there's interest.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/5197#issuecomment-148835254.

authors: AmplabJenkins JoshRosen andrewor14 chidouhu


text:
[SPARK-6154][streaming] Add Kafka modules to the 2.11 build.

This is somewhat related to SPARK-6154, though it only touches Kafka, not the jline dependency for thriftserver.
I tested this locally on 2.11 (./run-tests) and everything looked good (I had to disable mima, because MimaBuild harcodes 2.10 for the previous version -- that's another PR).

(changed the title to mention the ticket, though it doesn't fix all the issues mentioned there)

Can one of the admins verify this patch?

@pwendell Do you think we could still include this in 1.4? It's only adding the kafka modules to the 2.11 build, tests pass and no code changes were necessary.

Jenkins, test this please.

@dragos yeah I think it's fine - let's see if tests pass and I will merge it.

Merged build triggered.

Merged build started.

Test build #32838 has started for   PR 6149 at commit aa15d99.

Test build #32838 has finished for   PR 6149 at commit aa15d99.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Failed download during mima check... could this be a transient network issue? I can download from https://repo1.maven.org/maven2/org/apache/spark/spark-streaming-zeromq_2.10/1.2.0/spark-streaming-zeromq_2.10-1.2.0.jar without problems...
[info] 	[SUCCESSFUL ] org.apache.spark#spark-streaming-mqtt_2.10;1.2.0!spark-streaming-mqtt_2.10.jar (221ms)
[info] downloading https://repo1.maven.org/maven2/org/apache/spark/spark-streaming-zeromq_2.10/1.2.0/spark-streaming-zeromq_2.10-1.2.0.jar ...
[warn] 	[FAILED     ] org.apache.spark#spark-streaming-zeromq_2.10;1.2.0!spark-streaming-zeromq_2.10.jar: /home/jenkins/.ivy2/cache/org.apache.spark/spark-streaming-zeromq_2.10/jars/spark-streaming-zeromq_2.10-1.2.0.jar.part (No such file or directory) (221ms)
[warn] 	[FAILED     ] org.apache.spark#spark-streaming-zeromq_2.10;1.2.0!spark-streaming-zeromq_2.10.jar: /home/jenkins/.ivy2/cache/org.apache.spark/spark-streaming-zeromq_2.10/jars/spark-streaming-zeromq_2.10-1.2.0.jar.part (No such file or directory) (221ms)
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/org/apache/spark/spark-streaming-zeromq_2.10/1.2.0/spark-streaming-zeromq_2.10-1.2.0.jar
[info] downloading https://repo1.maven.org/maven2/org/apache/spark/spark-streaming-flume_2.10/1.2.0/spark-streaming-flume_2.10-1.2.0.jar ...
[info] 	[SUCCESSFUL ] org.apache.spark#spark-streaming-flume_2.10;1.2.0!spark-streaming-flume_2.10.jar (307ms)
[info] downloading https://repo1.maven.org/maven2/org/apache/spark/spark-streaming-kafka_2.10/1.2.0/spark-streaming-kafka_2.10-1.2.0.jar ...
[info] 	[SUCCESSFUL ] org.apache.spark#spark-streaming-kafka_2.10;1.2.0!spark-streaming-kafka_2.10.jar (232ms)
[info] downloading https://repo1.maven.org/maven2/org/apache/spark/spark-streaming-twitter_2.10/1.2.0/spark-streaming-twitter_2.10-1.2.0.jar ...
[info] 	[SUCCESSFUL ] org.apache.spark#spark-streaming-twitter_2.10;1.2.0!spark-streaming-twitter_2.10.jar (228ms)
[info] downloading https://repo1.maven.org/maven2/org/apache/spark/spark-streaming_2.10/1.2.0/spark-streaming_2.10-1.2.0.jar ...
[info] 	[SUCCESSFUL ] org.apache.spark#spark-streaming_2.10;1.2.0!spark-streaming_2.10.jar (463ms)
[info] downloading https://repo1.maven.org/maven2/org/apache/spark/spark-mllib_2.10/1.2.0/spark-mllib_2.10-1.2.0.jar ...
[info] 	[SUCCESSFUL ] org.apache.spark#spark-mllib_2.10;1.2.0!spark-mllib_2.10.jar (440ms)
[info] downloading https://repo1.maven.org/maven2/org/apache/spark/spark-bagel_2.10/1.2.0/spark-bagel_2.10-1.2.0.jar ...
[info] 	[SUCCESSFUL ] org.apache.spark#spark-bagel_2.10;1.2.0!spark-bagel_2.10.jar (231ms)
[info] downloading https://repo1.maven.org/maven2/org/apache/spark/spark-graphx_2.10/1.2.0/spark-graphx_2.10-1.2.0.jar ...
[info] 	[SUCCESSFUL ] org.apache.spark#spark-graphx_2.10;1.2.0!spark-graphx_2.10.jar (285ms)
[info] downloading https://repo1.maven.org/maven2/org/apache/spark/spark-core_2.10/1.2.0/spark-core_2.10-1.2.0.jar ...
[info] 	[SUCCESSFUL ] org.apache.spark#spark-core_2.10;1.2.0!spark-core_2.10.jar (851ms)
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::              FAILED DOWNLOADS            ::
[warn] 	:: ^ see resolution messages for details  ^ ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: org.apache.spark#spark-streaming-zeromq_2.10;1.2.0!spark-streaming-zeromq_2.10.jar
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
sbt.ResolveException: download failed: org.apache.spark#spark-streaming-zeromq_2.10;1.2.0!spark-streaming-zeromq_2.10.jar
	at sbt.IvyActions$.sbt$IvyActions$$resolve(IvyActions.scala:278)
	at sbt.IvyActions$$anonfun$updateEither$1.apply(IvyActions.scala:175)
	at sbt.IvyActions$$anonfun$updateEither$1.apply(IvyActions.scala:157)
	at sbt.IvySbt$Module$$anonfun$withModule$1.apply(Ivy.scala:151)
	at sbt.IvySbt$Module$$anonfun$withModule$1.apply(Ivy.scala:151)
	at sbt.IvySbt$$anonfun$withIvy$1.apply(Ivy.scala:128)
	at sbt.IvySbt.sbt$IvySbt$$action$1(Ivy.scala:56)
	at sbt.IvySbt$$anon$4.call(Ivy.scala:64)
	at xsbt.boot.Locks$GlobalLock.withChannel$1(Locks.scala:93)
	at xsbt.boot.Locks$GlobalLock.xsbt$boot$Locks$GlobalLock$$withChannelRetries$1(Locks.scala:78)
	at xsbt.boot.Locks$GlobalLock$$anonfun$withFileLock$1.apply(Locks.scala:97)
	at xsbt.boot.Using$.withResource(Using.scala:10)
	at xsbt.boot.Using$.apply(Using.scala:9)
	at xsbt.boot.Locks$GlobalLock.ignoringDeadlockAvoided(Locks.scala:58)
	at xsbt.boot.Locks$GlobalLock.withLock(Locks.scala:48)
	at xsbt.boot.Locks$.apply0(Locks.scala:31)
	at xsbt.boot.Locks$.apply(Locks.scala:28)
	at sbt.IvySbt.withDefaultLogger(Ivy.scala:64)
	at sbt.IvySbt.withIvy(Ivy.scala:123)
	at sbt.IvySbt.withIvy(Ivy.scala:120)
	at sbt.IvySbt$Module.withModule(Ivy.scala:151)
	at sbt.IvyActions$.updateEither(IvyActions.scala:157)
	at sbt.Classpaths$$anonfun$sbt$Classpaths$$work$1$1.apply(Defaults.scala:1318)
	at sbt.Classpaths$$anonfun$sbt$Classpaths$$work$1$1.apply(Defaults.scala:1315)
	at sbt.Classpaths$$anonfun$doWork$1$1$$anonfun$85.apply(Defaults.scala:1345)
	at sbt.Classpaths$$anonfun$doWork$1$1$$anonfun$85.apply(Defaults.scala:1343)
	at sbt.Tracked$$anonfun$lastOutput$1.apply(Tracked.scala:35)
	at sbt.Classpaths$$anonfun$doWork$1$1.apply(Defaults.scala:1348)
	at sbt.Classpaths$$anonfun$doWork$1$1.apply(Defaults.scala:1342)
	at sbt.Tracked$$anonfun$inputChanged$1.apply(Tracked.scala:45)
	at sbt.Classpaths$.cachedUpdate(Defaults.scala:1360)
	at sbt.Classpaths$$anonfun$updateTask$1.apply(Defaults.scala:1300)
	at sbt.Classpaths$$anonfun$updateTask$1.apply(Defaults.scala:1275)
	at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
	at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
	at sbt.std.Transform$$anon$4.work(System.scala:63)
	at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
	at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
	at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
	at sbt.Execute.work(Execute.scala:235)
	at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
	at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
	at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159)
	at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

Jenkins, retest this please.

Merged build triggered.

Merged build started.

Test build #32846 has started for   PR 6149 at commit aa15d99.

Test build #32846 has finished for   PR 6149 at commit aa15d99.

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/32846/
Test PASSed.

If we now support Kafka in 2.11, we should update the "Builds Spark for 2.11" instructions to reflect this: https://spark.apache.org/docs/latest/building-spark.html#building-for-scala-211.  Would be great to get an update in for 1.4.

authors: AmplabJenkins JoshRosen SparkQA dragos pwendell


text:
[SPARK-10740][SQL] handle nondeterministic expressions correctly for set operations

https://issues.apache.org/jira/browse/SPARK-10740

Merged build triggered.

Merged build started.

Test build #42794 has started for   PR 8858 at commit a1f41b5.

Test build #42794 has finished for   PR 8858 at commit a1f41b5.

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/42794/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #42799 has started for   PR 8858 at commit 555cf3b.

Test build #42799 has finished for   PR 8858 at commit 555cf3b.

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/42799/
Test PASSed.

LGTM. Merging to master and branch 1.5.

authors: AmplabJenkins SparkQA cloud-fan yhuai


text:
STORM-3204: Upgrade Metrics to 4.0.3

https://issues.apache.org/jira/browse/STORM-3204
The Metrics project has a BOM now, so we don't have to specify versions for each module or transitive dependency.
I used the one liner described here https://grep.codeconsult.ch/2010/07/08/list-all-your-maven-dependencies/ to get the list of dependencies for the entire project. The diff between master and this branch is posted below.
13c13
<     ch.qos.logback:logback-classic:jar:1.1.2
---
>     ch.qos.logback:logback-classic:jar:1.2.3
184a185
>     com.rabbitmq:amqp-client:jar:4.4.1
208c209
<  Finished at: 2018-08-25T09:00:50Z
---
>  Finished at: 2018-08-25T08:57:14Z
226,236c227,237
<     io.dropwizard.metrics:metrics-annotation:jar:4.0.2
<     io.dropwizard.metrics:metrics-core:jar:3.1.0
<     io.dropwizard.metrics:metrics-graphite:jar:3.1.0
<     io.dropwizard.metrics:metrics-healthchecks:jar:4.0.2
<     io.dropwizard.metrics:metrics-jersey2:jar:4.0.2
<     io.dropwizard.metrics:metrics-jetty9:jar:4.0.2
<     io.dropwizard.metrics:metrics-jmx:jar:4.0.2
<     io.dropwizard.metrics:metrics-json:jar:4.0.2
<     io.dropwizard.metrics:metrics-jvm:jar:4.0.2
<     io.dropwizard.metrics:metrics-logback:jar:4.0.2
<     io.dropwizard.metrics:metrics-servlets:jar:4.0.2
---
>     io.dropwizard.metrics:metrics-annotation:jar:4.0.3
>     io.dropwizard.metrics:metrics-core:jar:4.0.3
>     io.dropwizard.metrics:metrics-graphite:jar:4.0.3
>     io.dropwizard.metrics:metrics-healthchecks:jar:4.0.3
>     io.dropwizard.metrics:metrics-jersey2:jar:4.0.3
>     io.dropwizard.metrics:metrics-jetty9:jar:4.0.3
>     io.dropwizard.metrics:metrics-jmx:jar:4.0.3
>     io.dropwizard.metrics:metrics-json:jar:4.0.3
>     io.dropwizard.metrics:metrics-jvm:jar:4.0.3
>     io.dropwizard.metrics:metrics-logback:jar:4.0.3
>     io.dropwizard.metrics:metrics-servlets:jar:4.0.3
386a388
>     org.apache.httpcomponents:httpasyncclient:jar:4.1.3

The new amqp-client dependency is through metrics-graphite. It used to be optional in 3.1.0, now it isn't in 4.0.3. The httpasyncclient is in storm-elasticsearch, I'm not sure why it shows as new rather than changed (previous version was 4.1.2). The rest are just version changes for the metrics dependencies.

Need to look at this a bit more, there's an incompatibility with Cassandra's version of Metrics.

repo: apache/storm


text:
Time-Series Table results not sorting correctly

Columns in the Time-Series Table are not sorting correctly if results have N/A values.
How to reproduce the bug

Create a time series table chart
Add a metric, a group by, and a simple time series column (like time comparison with actual values)
Make sure some of the group by results don't have values resulting in N/As in the time series column
Sort using the arrows near the column title

Expected results
Results are sorted correctly
Actual results

Environment
(please complete the following information):

browser type and version:
superset version: near master
python version: python --version
node.js version: node -v
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

This is not a bug.Working as Expected. When select results having N/A values.
Screenshot:-
1.When update a chart

2.When click on sorted up arrow from Time-sries column ,it is sorting.

3.without selecting arrows

Loom video:-
https://www.loom.com/share/11d8e84b81624ee890f8e7606323ac2b

Sounds like this is fixed.... closing! Happy to review a new Issue if there are related bugs in 3.x or greater.

source: gharchive/issue

authors: ShaliniIruvuru michellethomas rusackas

repo: apache/superset


text:
Error: Referenced columns not available in DataFrame in Mixed Charts when one query has only nulls

Bug description
Creating a Mixed Chart using a dataset that yields only null values for one of the queries will produce an error
Unexpected error
Error: Referenced columns not available in DataFrame.

How to reproduce the bug
Consider the following dataset
-- to test issue with two charts when one dataset has only nulls

with part_a as (
SELECT *
FROM generate_series(1,100) as id),
part_b as (
  (
    select id,
    random() as value,
    'type_a' as some_type,
    '2001-10-22 00:00'::timestamp + (part_a.id::text || ' hours')::interval as ts
    from part_a
  )
  union all
  (
    select id,
    null as value,
    'type_b' as some_type,
    '2001-10-22 00:00'::timestamp + (part_a.id::text || ' hours')::interval as ts
    from part_a)
  )

select * from part_b;

which yields ts, value and some_type with 2 different types. The latter is null for one type and random for the other.
Create a Mixed Chart using this dataset, using these settings, will get an error

Now, if I remove the filter in the query B that yields only null values, then it works (not correctly though, because I wanted it to be filtered)

Screenshots/recordings
No response
Superset version
3.1.3
Python version
I don't know
Node version
I don't know
Browser
Firefox
Additional context
I'm using Superset version 3.0.2.
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

I'm experiencing the same issue; however, in my case, it's not due to just using a mixed chart but rather because one of the queries in the mixed chart applies a rolling function (I need a 'mean'). It doesn't happen to all types of charts, only to mixed charts that use rolling functions.

authors: Jockxtar diegoquintanav


text:
fix: Add french translation missing

SUMMARY
Adding french translation
Add Information
Fixes https://github.com/apache/superset/issues/20060

Hello @villebro,
I created 4 other pr from this one
I pinned you on each one, I hope to get your feedback

@mathieudruart it appears you need to fix some linting errors in the translation file:

hey @villebro, correction of workflow has been made, it's possible to launch it ?
Thanks

@mathieudruart it appears you need to fix some linting errors in the translation file:

Hi @villebro it should be fixed, is it possible to rerun the workflows ? Thanks !

Hi @villebro do you know when this PR will be merged ? thank you !

Hey @mathieudruart , sorry for the delay; merged!

authors: aehanno mathieudruart villebro


text:
[doc]: fixed small error

I only fixed a small typo error

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Closing this since it's a bit out of date. Thanks for the PR and sorry it slid under our collective radar. Some of this has been fixed elsewhere already. Since it's in need of a rebase, I'll close this and look into the sqllite one since that appears in a lot of places (not all of which might be wrong).


text:
fix(ComparisonRangeLabel): Add optional chaining to customTimeRangeComparisonFilters

SUMMARY

This is meant to the fix the error alert that is produced when a custom range is set. The value is now optional to wait for the promise. It is also added to currentTimeRangeFilters as a precaution.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

BEFORE:

AFTER:

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Hmm... wonder how this got merged with a failing lint check?

authors: rtexelm rusackas


text:
THRIFT-4854 oneway calls do not work over HTTP

Client: netstd
Patch: Jens Geyer

This is a generic issue across many of the language implementations.

repo: apache/thrift


text:
On Windows getJarLocation returns path like x:\tomee\bla\bla\bla

This is not ok for the code that uses this path and tries to convert it to URL.
For that reason a valid URL string must be returned from this method.
Also the cycle below cycles on ejb modules but generates result from appModule which is already covered before that. Am I wrong here on my assumption?

@doychin is there a test that fails without this change? It looks great - just wanted to check it here.

@jgallimore Yes, all tests for persistence in openejb-core.
The problem is that the path produced from old code is Windows path that is not directly compatible with URL format. And that path is passed to PersistenceModule constructor as rootUrl. So all tests related to CmpJpaConversion fail with exception
java.lang.IllegalArgumentException: Illegal character in opaque part at index 2: D:\tomee\container\openejb-core\target\TestModule

Here is a list of tests that fail in openejb-core only: OpenEjb2ConversionTest, SunCmpConversionTest, SimpleCmpTest, StatefulJPATest, JPACMDIntegrationTest

authors: doychin jgallimore

repo: apache/tomee


text:
Remove wrapper around response object

Closes: #6795
The API response incorrectly adds an additional response and alert wrapper. The API will now return a response as documented at /federations/{{id}}/federation_resolvers

Which Traffic Control components are affected by this PR?

Traffic Ops

What is the best way to verify this PR?

Federations can only be accessed via the API (or the client libraries). Attempt to POST a body with contents similar to:
{
	"fedResolverIds": [1],
	"replace": true
}

to the federations/{{id}}/federation_resolvers endpoint where the resolverIds matches existing resolvers and the {{id}} matches an existing federation.
If this is a bugfix, which Traffic Control versions contained the bug?

PR submission checklist

[ ] This PR has tests
[x] This PR has documentation - This fixes an endpoint to meet existing documentation
[x] This PR has a CHANGELOG.md entry
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Looks like the APIv4 tests are expecting the wrapped format.

repo: apache/trafficcontrol


text:
Fix edge cases for DSR creation, update, and deletion

There are currently two problems with DSRs in the legacy APIv3 that this PR fixes.

Creating or deleting a DSR using APIv3 will work as intended, but returns an incorrect response body. It will erroneously use an APIv4 structure in the response.
Creating or updating a DSR in APIv3 without the required deliveryservice property triggers a 500 Internal Server Error, response. It should instead complain that the required field was not present.

Which Traffic Control components are affected by this PR?

Traffic Ops

What is the best way to verify this PR?
Make sure the provided tests pass. You can test manually by just doing the things outlined above that caused the issue.
If this is a bugfix, which Traffic Control versions contained the bug?

master

PR submission checklist

[x] This PR has tests
[x] This PR doesn't need documentation
[x] This PR doesn't need a CHANGELOG.md entry
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

Originally I had added a TO Go client integration test case to make sure the response contained a deliveryService property, but our client drops the response so checking that is impossible without either a breaking change to the client, or adding functionality to a client of deprecated API. Neither of which I'm willing to do.
I really wish I had realized that earlier, because the only reason I modified code in lib/ was to enable that test, which is now unnecessary. But I'm leaving it in as it's a change that was requested in one of my PRs last year.


text:
Au test post-early-return fails sporadically for HTTP/2 client

I change the test to enable debug output for tag http2_stream.   I ran the test 80 times, and it failed 5 times.  I removed the timestamp and event thread number from the output.  This is the output for (all) the failed runs:
<Http2Stream.cc:376 (change_state)> (http2_stream) [4] [1] Http2StreamState::HTTP2_STREAM_STATE_OPEN
<Http2Stream.cc:376 (change_state)> (http2_stream) [4] [1] Http2StreamState::HTTP2_STREAM_STATE_HALF_CLOSED_LOCAL
<Http2Stream.cc:376 (change_state)> (http2_stream) [4] [1] Http2StreamState::HTTP2_STREAM_STATE_CLOSED
<Http2Stream.cc:434 (do_io_close)> (http2_stream) [4] [1] do_io_close
<Http2Stream.cc:68 (~Http2Stream)> (http2_stream) [4] [1] Destroy stream, sent 0 bytes

The output for the successful runs was either (16 runs):
<Http2Stream.cc:376 (change_state)> (http2_stream) [4] [1] Http2StreamState::HTTP2_STREAM_STATE_OPEN
<Http2Stream.cc:376 (change_state)> (http2_stream) [4] [1] Http2StreamState::HTTP2_STREAM_STATE_HALF_CLOSED_LOCAL
<Http2Stream.cc:434 (do_io_close)> (http2_stream) [4] [1] do_io_close
<Http2Stream.cc:68 (~Http2Stream)> (http2_stream) [4] [1] Destroy stream, sent 0 bytes
<Http2Stream.cc:376 (change_state)> (http2_stream) [4] [1] Http2StreamState::HTTP2_STREAM_STATE_CLOSED

or (59 runs):
<Http2Stream.cc:376 (change_state)> (http2_stream) [4] [1] Http2StreamState::HTTP2_STREAM_STATE_OPEN
<Http2Stream.cc:376 (change_state)> (http2_stream) [4] [1] Http2StreamState::HTTP2_STREAM_STATE_HALF_CLOSED_REMOTE
<Http2Stream.cc:376 (change_state)> (http2_stream) [4] [1] Http2StreamState::HTTP2_STREAM_STATE_CLOSED
<Http2Stream.cc:434 (do_io_close)> (http2_stream) [4] [1] do_io_close
<Http2Stream.cc:68 (~Http2Stream)> (http2_stream) [4] [1] Destroy stream, sent 0 bytes

The commit (on master) I built to do this test:  4547ed75cb882f47f30c9370a685489c57ae773d
config.nice:
#! /bin/sh
#
# Created by configure

CFLAGS=" "; export CFLAGS
CXXFLAGS=" "; export CXXFLAGS
LDFLAGS="-L/opt/oath/libssh2/1.8/lib -L/opt/oath/nghttp2/1.36/lib"; export LDFLAGS
"./configure" \
"--with-openssl=/opt/oath/openssl/1.1.1" \
"--enable-experimental-plugins" \
"--enable-example-plugins" \
"--with-brotli=/opt/oath/brotli/1.0/include:/opt/oath/brotli/1.0/lib" \
"--enable-ccache" \
"--enable-werror" \
"--prefix=/Users/wkaras/TSX/TS4" \
"--exec-prefix=/Users/wkaras/TSX/TS4" \
"PKG_CONFIG_PATH=/opt/rh/devtoolset-8/root/usr/lib64/pkgconfig:/opt/rh/httpd24/root/usr/lib64/pkgconfig:/opt/rh/rh-python36/root/usr/lib64/pkgconfig:/opt/rh/devtoolset-8/root/usr/lib64/pkgconfig:/opt/rh/httpd24/root/usr/lib64/pkgconfig:/opt/rh/devtoolset-8/root/usr/lib64/pkgconfig" \
"CFLAGS=" \
"LDFLAGS=-L/opt/oath/libssh2/1.8/lib -L/opt/oath/nghttp2/1.36/lib" \
"CXXFLAGS=" \
"$@"

This was on RHEL7 (with mysterious Yahoo hacks) and devtoolset 8.

The error output of the (verbose) failed curl command is:
*   Trying 127.0.0.1:61311...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to 127.0.0.1 (127.0.0.1) port 61311 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [15 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [873 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=IE; ST=Dublin; L=Dublin; O=example.com; OU=example.com; CN=example.com
*  start date: Jan 26 14:56:08 2021 GMT
*  expire date: Aug 21 14:56:08 2119 GMT
*  issuer: C=IE; ST=Dublin; L=Dublin; O=example.com; OU=example.com; CN=example.com
*  SSL certificate verify result: self signed certificate (18), continuing anyway.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x1523ad0)
} [5 bytes data]
> POST /post-http2 HTTP/2
> Host: 127.0.0.1:61311
> user-agent: curl/7.79.0-DEV
> accept: */*
> content-length: 2310700
> content-type: application/x-www-form-urlencoded
>
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* old SSL session ID is stale, removing
} [5 bytes data]
< HTTP/2 420
< content-length: 0
< date: Wed, 17 Nov 2021 20:19:03 GMT
< age: 0
< server: ATS/10.0.0
* HTTP error before end of send, stop sending
<
* HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)
* stopped the pause stream!
 61 2256k    0     0   61 1391k      0  60.0M --:--:-- --:--:-- --:--:-- 61.7M
* Connection #0 to host 127.0.0.1 left intact
curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)

This is the bash script I used to find the three unique cases:
rm -rf /tmp/dir
mkdir /tmp/dir
mkdir /tmp/dir/link

let N=0
for I in $( seq 1 80 )
do
  fgrep DEBUG: xyz$I/_output/*ts/*all* | sed 's/^.*DEBUG: //' >| /tmp/dir/tmp
  let F=0
  if (( N != 0 )) ; then
    for I2 in $( seq 1 $N )
    do
      cmp /tmp/dir/tmp /tmp/dir/out$I2
      if (( $? == 0 )) ; then
        ln -s /tmp/dir/out$I2 /tmp/dir/link/out$I
        let F=1
        break
      fi
    done
  fi
  if (( F == 0 )) ; then
    let N=N+1
    mv /tmp/dir/tmp /tmp/dir/out$N
    ln -s /tmp/dir/out$N /tmp/dir/link/out$I
  fi
done

I suppose the INTERNAL_ERROR came from here:
https://github.com/apache/trafficserver/blob/4547ed75cb882f47f30c9370a685489c57ae773d/proxy/http2/Http2ConnectionState.cc#L181-L184

If anyone wants to try to reproduce this, the way I run the same test back to back, multiple times, is to first cd to the directory containing the test, and create aliases for it using symbolic links:
for n in $( seq 1 100 ); do ln -s post-early-return.test.py xyz$n.test.py; done

Then cd to the TS tests subdirectory, and run the test multiple times using the aliases:
./autest.sh --ats-bin ~/TSX/TS4/bin -f $( for n in $( seq 1 80 ) ; do echo xyz$n ; done )

I will retest, and close if the failures are no longer present.

In my environment, this test seems to be working worse now than before.  But seems to work OK in open source CI Au test regression run.

authors: maskit ywkaras

repo: apache/trafficserver


text:
HTTP/2 specific error code=0x0b

ATS 10 diags log
[Mar 18 18:20:46.163] [ET_NET 6] ERROR: HTTP/2 connection error code=0x0b client_ip=x.x.x.x session_id=44554 stream_id=0 Erroneous client window update

from RFC "The endpoint detected that its peer is exhibiting a behavior that might be generating excessive load."
Can this be fixed with the escalation plugin? If so, what is the error code that needs to be specified in order for it to work. Perhaps other settings that allow less load on origin?

Do you have details on how to reproduce this issue?

I second this: your reproduction steps would be helpful. I notice in the HTTP/2 to origin branch (#9366), the source code that would reply with this is commented out:
https://github.com/apache/trafficserver/pull/9366/files#diff-4229308c46f79900709a78c541d8de01a25fffe8073673ac798828517d879f30R2651
Are you perhaps running gRPC?
This issue may, therefore, go away for you once we merge in HTTP/2 to origin PR. That should land in 10.x

Do you have details on how to reproduce this issue?

I second this: your reproduction steps would be helpful. I notice in the HTTP/2 to origin branch (#9366), the source code that would reply with this is commented out:
https://github.com/apache/trafficserver/pull/9366/files#diff-4229308c46f79900709a78c541d8de01a25fffe8073673ac798828517d879f30R2651
Are you perhaps running gRPC?
This issue may, therefore, go away for you once we merge in HTTP/2 to origin PR. That should land in 10.x

not gRPC
Thank you, I will try this too.
Based on my observations, the average response time for HTTP/2 is 3-4 times better. However, while I used to be able to run the configuration on 8GB of memory, with HTTP/2 enabled, the memory runs out during periods of high loads.

The reduction of the default value by half for the option proxy.config.http2.min_avg_window_update did not change anything.

min_avg_window_update is to protect ATS from DoS attack, so you can change it to 1 with a risk if you need.
Appropriate value depends on your use case. For example, if data was going to be transferred intermittently like 100 bytes, pause, 100 bytes, pause ..., then you'd have to set min_avg_window_update to 100 or less.

min_avg_window_update is to protect ATS from DoS attack, so you can change it to 1 with a risk if you need.
Appropriate value depends on your use case. For example, if data was going to be transferred intermittently like 100 bytes, pause, 100 bytes, pause ..., then you'd have to set min_avg_window_update to 100 or less.

If this works, then it means there's a problem with the default parameter. I have regular HLS traffic. The client requests a new file every 5-10 seconds. And there are massive triggers from thousands of different IPs in the log. Let's check. Thank you for your help.

CONFIG proxy.config.http2.min_avg_window_update FLOAT 1.0
This value solves my problem. The logs are clean. However, it's unclear why this is happening, considering there was no DDOS, only regular users and HLS traffic.

authors: bneradt cheluskin maskit


text:
[TOPI] batch_matmul cannot use and / or / not operator to Expr

I try to use topi.nn.batch_matmul, following the instruction here. It requires input type tvm.te.Tensor. However, the following code incurs error.
import tvm
import torch
from tvm import topi
from tvm import te

def main():

    b = te.var("b")
    n = te.var("n")
    d = te.var("d")

    a = te.placeholder((b, n, d), dtype="float32", name="a")
    b = te.placeholder((b, n, d), dtype="float32", name="b")

    print(type(a))

    c = topi.nn.batch_matmul(a, b)
    print(c)

if __name__ == "__main__":
    main()

Traceback (most recent call last):
  File "bmm.py", line 19, in <module>
    main()
  File "bmm.py", line 15, in main
    c = topi.nn.batch_matmul(a, b)
  File "/home/jojo6174/tvm-installation/tvm/python/tvm/topi/nn/batch_matmul.py", line 54, in batch_matmul
    batch = max(XB, YB)
  File "/home/jojo6174/tvm-installation/tvm/python/tvm/tir/expr.py", line 176, in __bool__
    return self.__nonzero__()
  File "/home/jojo6174/tvm-installation/tvm/python/tvm/tir/expr.py", line 172, in __nonzero__
    + "use tvm.tir.all / tvm.tir.any instead"
ValueError: Cannot use and / or / not operator to Expr, hint: use tvm.tir.all / tvm.tir.any instead

I found that in tvm/python/tvm/topi/nn/batch_matmul.py. A python built-in max is called, however, the argumenets type seems incompatible. I modified it to te.max solved the problem. Is there any misunderstanding here? Thanks!

Thanks for reporting the issue.  I think it is te.max. Could you send a PR?

@zhiics Sure! I will send it later

@tsupei , @zhiics
How about this? by this, we can test.
Patch is here.
From 9b7b1589f4a05a739e19652b7a2705e4bfc7bfcb Mon Sep 17 00:00:00 2001
From: Insop Song <insop.song@gmail.com>
Date: Wed, 16 Dec 2020 01:19:04 -0800
Subject: [PATCH] Add test to dynamic batch matmul

---
 .../topi/python/test_topi_batch_matmul.py     | 38 ++++++++++++++++---
 1 file changed, 32 insertions(+), 6 deletions(-)

diff --git a/tests/python/topi/python/test_topi_batch_matmul.py b/tests/python/topi/python/test_topi_batch_matmul.py
index e939f6c21..be6552f03 100644
--- a/tests/python/topi/python/test_topi_batch_matmul.py
+++ b/tests/python/topi/python/test_topi_batch_matmul.py
@@ -32,10 +32,24 @@ _batch_matmul_implement = {
 }

-def verify_batch_matmul(x_batch, y_batch, M, N, K):
-    x = te.placeholder((x_batch, M, K), name="x")
-    y = te.placeholder((y_batch, N, K), name="y")
-    dtype = x.dtype
+def verify_batch_matmul(x_batch, y_batch, M, N, K, dynamic=False, debug=False):
+
+    if not dynamic:
+        x = te.placeholder((x_batch, M, K), name="x")
+        y = te.placeholder((y_batch, N, K), name="y")
+        dtype = x.dtype
+    else:
+        assert x_batch == y_batch or x_batch == 1 or y_batch == 1
+        batch_size = max(x_batch, y_batch)
+        dynamic_batch_size = te.var("dynamic_batch_size")
+        dynamic_M = te.var("dynamic_M")
+        dynamic_N = te.var("dynamic_N")
+        dynamic_K = te.var("dynamic_K")
+
+        x = te.placeholder((dynamic_batch_size, dynamic_M, dynamic_K), name="x")
+        y = te.placeholder((dynamic_batch_size, dynamic_N, dynamic_K), name="y")
+        dtype = x.dtype
+

     # use memoize to pickle the test data for next time use
     @memoize("topi.tests.test_topi_batch_matmul")
@@ -53,10 +67,19 @@ def verify_batch_matmul(x_batch, y_batch, M, N, K):
         with tvm.target.Target(device):
             fcompute, fschedule = tvm.topi.testing.dispatch(device, _batch_matmul_implement)
             out = fcompute(x, y)
-            s = fschedule([out])
+            if not dynamic:
+                s = fschedule([out])
+                out_shape = out.shape
+            else:
+                s = te.create_schedule(out.op)
+                out_shape = (batch_size, M, N)
+
+            if debug:
+                print(tvm.lower(s, [x, y, out], simple_mode=True))
+
         a = tvm.nd.array(a_np, ctx)
         b = tvm.nd.array(b_np, ctx)
-        c = tvm.nd.array(np.zeros(get_const_tuple(out.shape), dtype=dtype), ctx)
+        c = tvm.nd.array(np.zeros(get_const_tuple(out_shape), dtype=dtype), ctx)
         f = tvm.build(s, [x, y, out], device, name="dense")
         f(a, b, c)
         tvm.testing.assert_allclose(c.asnumpy(), c_np, rtol=1e-5)
@@ -75,6 +98,9 @@ def test_batch_matmul():
     verify_batch_matmul(1, 5, 16, 16, 32)
     verify_batch_matmul(5, 1, 16, 16, 32)

+    # Test dynamic batch
+    verify_batch_matmul(1, 1, 16, 16, 32, dynamic=True, debug=True)
+    verify_batch_matmul(5, 5, 16, 16, 32, dynamic=True)

 if __name__ == "__main__":
     test_batch_matmul()
--
2.28.0

Test restults
$ python ./test_topi_batch_matmul.py
Running on target: llvm -device=arm_cpu
Cannot find config for target=llvm -keys=arm_cpu,cpu -device=arm_cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (1, 16, 32), 'float32'), ('TENSOR', (1, 16, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm
Cannot find config for target=llvm -keys=cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (1, 16, 32), 'float32'), ('TENSOR', (1, 16, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm -device=arm_cpu
Cannot find config for target=llvm -keys=arm_cpu,cpu -device=arm_cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (5, 16, 32), 'float32'), ('TENSOR', (5, 16, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm
Cannot find config for target=llvm -keys=cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (5, 16, 32), 'float32'), ('TENSOR', (5, 16, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm -device=arm_cpu
Cannot find config for target=llvm -keys=arm_cpu,cpu -device=arm_cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (5, 16, 32), 'float32'), ('TENSOR', (5, 20, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm
Cannot find config for target=llvm -keys=cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (5, 16, 32), 'float32'), ('TENSOR', (5, 20, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm -device=arm_cpu
Cannot find config for target=llvm -keys=arm_cpu,cpu -device=arm_cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (30, 16, 32), 'float32'), ('TENSOR', (30, 20, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm
Cannot find config for target=llvm -keys=cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (30, 16, 32), 'float32'), ('TENSOR', (30, 20, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm -device=arm_cpu
Cannot find config for target=llvm -keys=arm_cpu,cpu -device=arm_cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (1, 16, 32), 'float32'), ('TENSOR', (5, 16, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm
Cannot find config for target=llvm -keys=cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (1, 16, 32), 'float32'), ('TENSOR', (5, 16, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm -device=arm_cpu
Cannot find config for target=llvm -keys=arm_cpu,cpu -device=arm_cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (5, 16, 32), 'float32'), ('TENSOR', (1, 16, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm
Cannot find config for target=llvm -keys=cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (5, 16, 32), 'float32'), ('TENSOR', (1, 16, 32), 'float32')). A fallback configuration is used, which may bring great performance regression.
Running on target: llvm -device=arm_cpu
Cannot find config for target=llvm -keys=arm_cpu,cpu -device=arm_cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (dynamic_batch_size, dynamic_M, dynamic_K), 'float32'), ('TENSOR', (dynamic_batch_size, dynamic_N, dynamic_K), 'float32')). A fallback configuration is used, which may bring great performance regression.
primfn(x_1: handle, y_1: handle, compute_1: handle) -> ()
  attr = {"global_symbol": "main", "tir.noalias": True}
  buffers = {compute: Buffer(compute_2: Pointer(float32), float32, [dynamic_batch_size: int32, dynamic_M: int32, dynamic_N: int32], [stride: int32, stride_1: int32, stride_2: int32], type="auto"),
             y: Buffer(y_2: Pointer(float32), float32, [dynamic_batch_size, dynamic_N, dynamic_K: int32], [stride_3: int32, stride_4: int32, stride_5: int32], type="auto"),
             x: Buffer(x_2: Pointer(float32), float32, [dynamic_batch_size, dynamic_M, dynamic_K], [stride_6: int32, stride_7: int32, stride_8: int32], type="auto")}
  buffer_map = {x_1: x, y_1: y, compute_1: compute} {
  for (b: int32, 0, dynamic_batch_size) {
    for (i: int32, 0, dynamic_M) {
      for (j: int32, 0, dynamic_N) {
        compute_2[(((b*stride) + (i*stride_1)) + (j*stride_2))] = 0f32
        for (k: int32, 0, dynamic_K) {
          compute_2[(((b*stride) + (i*stride_1)) + (j*stride_2))] = ((float32*)compute_2[(((b*stride) + (i*stride_1)) + (j*stride_2))] + ((float32*)x_2[(((b*stride_6) + (i*stride_7)) + (k*stride_8))]*(float32*)y_2[(((b*stride_3) + (j*stride_4)) + (k*stride_5))]))
        }
      }
    }
  }
}

Running on target: llvm
Cannot find config for target=llvm -keys=cpu -link-params=0, workload=('batch_matmul.x86', ('TENSOR', (dynamic_batch_size, dynamic_M, dynamic_K), 'float32'), ('TENSOR', (dynamic_batch_size, dynamic_N, dynamic_K), 'float32')). A fallback configuration is used, which may bring great performance regression.
primfn(x_1: handle, y_1: handle, compute_1: handle) -> ()
  attr = {"global_symbol": "main", "tir.noalias": True}
  buffers = {y: Buffer(y_2: Pointer(float32), float32, [dynamic_batch_size: int32, dynamic_N: int32, dynamic_K: int32], [stride: int32, stride_1: int32, stride_2: int32], type="auto"),
             compute: Buffer(compute_2: Pointer(float32), float32, [dynamic_batch_size, dynamic_M: int32, dynamic_N], [stride_3: int32, stride_4: int32, stride_5: int32], type="auto"),
             x: Buffer(x_2: Pointer(float32), float32, [dynamic_batch_size, dynamic_M, dynamic_K], [stride_6: int32, stride_7: int32, stride_8: int32], type="auto")}
  buffer_map = {x_1: x, y_1: y, compute_1: compute} {
  for (b: int32, 0, dynamic_batch_size) {
    for (i: int32, 0, dynamic_M) {
      for (j: int32, 0, dynamic_N) {
        compute_2[(((b*stride_3) + (i*stride_4)) + (j*stride_5))] = 0f32
        for (k: int32, 0, dynamic_K) {
          compute_2[(((b*stride_3) + (i*stride_4)) + (j*stride_5))] = ((float32*)compute_2[(((b*stride_3) + (i*stride_4)) + (j*stride_5))] + ((float32*)x_2[(((b*stride_6) + (i*stride_7)) + (k*stride_8))]*(float32*)y_2[(((b*stride) + (j*stride_1)) + (k*stride_2))]))
        }
      }
    }
  }
}

closed by #7111

authors: insop tsupei zhiics

repo: apache/tvm


text:
[BugFix][Driver] Correctly propogate simple-mode flag in LowerSchedule

Currently one version of tvm::LowerSchedule doesn't pass along the input simple_mode flag, which causes it to default back to false. This commit fixes it by passing along the input flag.

Thanks for sending this! Would it be possible that we can add some tests with simple_mode set to true/false? Otherwise LGTM.

Thanks. I did look into existing tests for LowerSchedule or tvm.lower, unfortunately none of them really tests simple_mode, which seems to be a convenience flag for debugging/testing purposes.
I could write a simple tvm.lower(..., simple_mode=...) unittest, but it actually doesn't go through this problematic version of LowerSchedule, which is only used here and here, and they don't even use the simple_mode flag.
I feel like the testing effort here isn't well worth it, but let me know what you think:).


text:
[Relay] Convert negative axes to positive when importing ONNX Unsqueeze

Currently, ONNX frontend imports Unsqueeze as a sequence of expand_dims in Relay. This works fine when the axes are positive.
However, for negative axes we need to compute the output rank and add the negative axis value to get its equivalent positive axis value.
This commit computes the output rank as the sum of the input rank of data and the number of axis in the axes array and convert negative axes to positive.
This commit also adds testcases for unsqueeze with negative axes and verifies the result with onnx runtime.

@AndrewZhaoLuo : This is my first pull request. Can you please take a look?


text:
[UNOMI-722] - Update Yauaa to 7.9.0 (CVE-2022-23496)

PR Title format:
[UNOMI-722] Update Yauaa to 7.9.0

Update this dependency because of CVE-2022-23496

[x] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Format the pull request title like [UNOMI-XXX] - Title of the pull request
[x] Provide integration tests for your changes, especially if you are changing the behavior of existing code or adding
significant new parts of code.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
Copy the description to the related JIRA issue
[x] Run mvn clean install -P integration-tests to make sure basic checks pass. A more thorough check will be
performed on your pull request automatically.

Trivial changes like typos do not require a JIRA issue (javadoc, project build changes, small doc changes, comments...).
If this is your first contribution, you have to read the Contribution Guidelines
If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.
To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

I found that org.brotli.dec was added by httpcomponents-client v5.2.1.
https://github.com/apache/httpcomponents-client/commit/db47570efefe32054f6d5a45cf0023e9d6927338
Looking at their code I see they have already indicated this is optional (and my code does not need it at all):
    <dependency>
      <groupId>org.brotli</groupId>
      <artifactId>dec</artifactId>
      <optional>true</optional>
    </dependency>

I'm going to find a fix for this.

@jkevan Which test gave this error? I'm having a hard time running the full build locally to reproduce the effect.

@jkevan Please check if this is correct now.

I'm going to see if I can get rid of this dependency that I do not need within Yauaa.

Seem's good to me now that the dependency is optional.

authors: jkevan nielsbasjes

repo: apache/unomi


text:
[YUNIKORN-2414] Embeds fontawesome and roboto

What is this PR for?
This PR embeds Fontawesome and Google Roboto as part of the project.
This allows web UI to run in internal networks without access to the public.
What type of PR is it?
[x] - Improvement
What is the Jira issue?
YUNIKORN-2414

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

Comparison is base (52625cf) 73.07% compared to head (974338b) 73.07%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #170   +/-   ##
=======================================
  Coverage   73.07%   73.07%
=======================================
  Files           1        1
  Lines          26       26
=======================================
  Hits           19       19
  Misses          4        4
  Partials        3        3

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

We need to check the license of the inclusions. Not all licenses are allowed: https://www.apache.org/legal/resolved.html
the pacakge typeface-roboto has been deprecated and we should move to fontsource-roboto as per the readme: https://classic.yarnpkg.com/en/package/typeface-roboto#readme

material-design-icons is Apache 2.0 (OK)
fontsource-roboto is Apache 2.0 (OK)
fontawesome is mixed MIT / CC / SIL OFL 1.1 License (class B,  maybe OK in binary form)

What are we using from the fontawesome-free package? Icons or fonts

This is a tricky one. We are using icons. The way we are using them is with CSS classes to render them from the font file. I had to look this up and this is what I got about the subject:

When you use CSS classes to display icons from a library like Font Awesome, the license that applies would be the one covering the use of the icons themselves.
In the case of Font Awesome Free, the icons are licensed under the Creative Commons Attribution 4.0 International license (CC BY 4.0). So, even if you are using CSS classes to display those icons, the CC BY 4.0 license still applies.
This means you are free to use, share, and adapt those icons for any purpose, including commercially, as long as you provide appropriate attribution.

Based on the changes we are only including the icons in the "convenience binary", i.e. the docker images, that we build.
We do need attribution of what we include, which means a NOTICE file etc in our docker images that we build. This would require a change in the way we build the image. It does not stop us from doing this.
In short: yes we can do this, but not 2 days out of the release branching etc for YuniKorn 1.5.
Tagging the jira for YuniKorn 1.6, we can commit the change after we branch.

Based on the changes we are only including the icons in the "convenience binary", i.e. the docker images, that we build. We do need attribution of what we include, which means a NOTICE file etc in our docker images that we build. This would require a change in the way we build the image. It does not stop us from doing this.

I don't think this requires any changes at all. One of the features of Angular is an auto-generated 3rdpartylibraries.txt file at the root of the generated content -- I've checked using this PR, and fontawesome gets included there along with the appropriate license text, so I believe we are covered on the attribution front. You can even pull this up from a running yunikorn-web instance via http://localhost:9889/3rdpartylicenses.txt

authors: codecov-commenter craigcondit dcoric wilfred-s

repo: apache/yunikorn-web


text:
[ZEPPELIN-1127] Show error message in case of exception with JDBC

What is this PR for?
When there is exception while executeSql in JDBC interpreter, only stack trace is sent back to UI, it should include e.getMessage() as well.
What type of PR is it?
[Improvement]
What is the Jira issue?

ZEPPELIN-1127

How should this be tested?
Create a paragraph, and write following and try to run
%phoenix
select * from a_table_not_there

You should see below, followed by stack trace
ERROR 1012 (42M03): Table undefined. tableName=A_TABLE_NOT_THERE

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

LGTM

LGTM

Merging this if no more discussion.

LGTM. @prabhjyotsingh Can this be merged into branch-0.6, too?

Sure @Leemoonsoo I'll do that.

authors: Leemoonsoo jongyoul prabhjyotsingh r-kamath

repo: apache/zeppelin

license_source: bigquery


text:
[ZEPPELIN-4600] nullpoint error in the long time process use api to run a note

What is this PR for?
Fix the stability problem of zengin for long time (7day) loop working ,
release the thread pools and socket connection when the interprether is closed
the same bug was found in the version 0.81 and 0.82
What type of PR is it?
[Bug Fix]
Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4600
How should this be tested?

Single tast works 30 hours with 7 second delay, test passed.

Screenshots (if appropriate)
Questions:

Does the licenses files need update?No
Is there breaking changes for older versions?No
Does this needs documentation?No

Thanks @tylerba-f  Overall PR LGTM, I leave some minor issue comments

code style adjust over

Thanks @tylerba-f for quick fix, have you verified this PR and how ?
BTW, it think its better to rename the JIRA ticket to be 'Socket connection between zeppelin server and interpreter is not closed properly'

Thanks @tylerba-f for quick fix, have you verified this PR and how ?
BTW, it think its better to rename the JIRA ticket to be 'Socket connection between zeppelin server and interpreter is not closed properly'

Thanks @tylerba-f for quick fix, have you verified this PR and how ?
BTW, it think its better to rename the JIRA ticket to be 'Socket connection between zeppelin server and interpreter is not closed properly'

And could you create another PR for master branch ?

@tylerba-f Could you update the PR title as well  ?

master branch PR was commited

Thanks, will merge it if no more comment

@tylerba-f Could you close this PR ? It has been merged already

ok

authors: tylerba-f zjffdu


text:
[ZEPPELIN-5869] Remove Incubating from Kyuubi reference

What is this PR for?
This PR is proposes to remove incubating from Kyuubi reference, since the ASF board has approved a resolution to graduate Kyuubi into a full Top Level Project.
https://github.com/apache/kyuubi/issues/4020
What type of PR is it?
Documentation
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-5869
How should this be tested?

Strongly recommended: add automated unit tests for any new or changed behavior
Outline any manual steps to test the PR here.

It's docs only change.
Screenshots (if appropriate)
Questions:

Does the license files need to update? No.
Is there breaking changes for older versions? No.
Does this needs documentation? No.

cc @zjffdu @huage1994

@huage1994 Could you please merge this PR if you have a permission now? 😃

@huage1994 Could you please merge this PR if you have a permission now? 😃 of course, after all reviews finish.

Yeah sure. I'll merge this PR after all reviews finish.

PR looks good to me. Do we want to wait until artifacts also lose the incubating suffix before making the change?

Hi @pan3793.  Does Kyuubi Community plan to release a new version without -incubating suffix for org.apache.kyuubi:kyuubi-hive-jdbc-shaded  in the very near future？

PR looks good to me. Do we want to wait until artifacts also lose the incubating suffix before making the change?

Hi @pan3793. Does Kyuubi Community plan to release a new version without -incubating suffix for org.apache.kyuubi:kyuubi-hive-jdbc-shaded in the very near future？

If not, I tend to merge this PR first.   @Reamer WDYT ?

For the above issue, we need to wait for releasing non-incubating version so that we could build ours without errors.

Hi @pan3793. Does Kyuubi Community plan to release a new version without -incubating suffix for org.apache.kyuubi:kyuubi-hive-jdbc-shaded in the very near future？

maybe after one month

... we need to wait for releasing non-incubating version so that we could build ours without errors.

Will this cause build failure?

oh.. Sorry, I misunderstand. It's totally not to break our build.

Will merge if no more comment

This PR is proposes to remove incubating from Kyuubi reference, since the ASF board has approved a resolution to graduate Kyuubi into a full Top Level Project.


text:
fix for opensearch release 2.1.0

currently the release 2.1.0 is broken, because a version was not updated in the build.gradle
i fixed this and also changed the version in the gradle.properties to the correct release versions, how plugins should be versioned
i am not able to build and test this, so feedback is welcome

Hi @Maglore,
the command that I use to build are the following ones:
./gradlew clean assemble -Dorg.gradle.java.home=/usr/lib/jvm/java-11-openjdk-amd64/

(the java version is mandatory)
and to release I use gh command:
gh release create 2.1.0.0 ./build/distributions/opensearch-analysis-ik-2.1.0.0.zip -t "2.1.0.0" --notes "IK Analysis for OpenSearch 2.1.0 fixed version"

I hope to help you.
Regards,
Alberto

authors: Maglore aparo

repo: aparo/opensearch-analysis-ik


text:
Fix text mistake (Mongodb -> Redis)

Hi,
I fix a little mistake on documentation for Redis Authentication Events.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant wouldsmina

repo: apereo/cas


text:
Replace use of Libav with FFmpeg

Is your feature request related to a problem? Please describe.
oEQ currently requires Libav for creation of thumbnails and previews of videos. However, linux distributions have deprecated this, with it being replaced with FFmpeg.
Describe the solution you'd like
One of:

Replace the hardcoded executable names with the FFmpeg equivalent;
Externalise the executables names (not just paths) into configuration for easy updating - maybe in another decade FFmpeg will be deprecated; or
Externalise the whole command...

Additional context
For now there is the work around (symlinking) as mentioned in #676 . So we can wait until a future milestone. We should consider some doco updates though.

It could also be worth considering using an existing JVM binding for ffmpeg, like https://github.com/bramp/ffmpeg-cli-wrapper
Which can provide a more idiomatic  API, additional validation, simpler progress reporting, and better error reporting.

I have this issue running openEquella on Ubunutu 18.04. Any updates on this would definetely help. Also for the workaround, since i am new on Linux, a proper working solution for symlinking would be of huge help.

@cbeach47 In the last dev meeting I couldn't somehow unmute my audio. Sorry about that.
Yes this is the same issue that was being discussed. I hope this will be fixed in the upcoming releases.
Also can you please confirm if this going to be fixed in the coming release or in later releases.

authors: Abdullah8006 ChristianMurphy abdkhanEummena edalex-ian

repo: apereo/openEQUELLA


text:
Add class to tooltip when x exceeds gridWidth

Is your feature request related to a problem? Please describe.
I'm trying to position the tooltip over the mouse cursor with css, but when x exceeds grid width it changes the way calculates position and my css rules place the tooltip too much to the left.
Describe the solution you'd like
Add class to tooltip when x exceeds gridWidth (Intersect.js), might be when an option is provided (so not by default):
      ttCtx.tooltip.classList.remove('_the_new_class_name')
      if (x + ttCtx.tooltipRect.ttWidth > w.globals.gridWidth) {
        x = x - ttCtx.tooltipRect.ttWidth;
        ttCtx.tooltip.classList.add('_the_new_class_name')
      }

Describe alternatives you've considered
It would be great to have tooltip position options in config.
Additional context
Great lib, many thanks.

@fcubria  I will add an option to position tooltip in the center (over the data point) along with left/right positions. The center option will not take into consideration whether the tooltip exceeds the gridWidth or not.
Thanks for the suggestion.

authors: fcubria junedchhipa

license: MIT


text:
Fix warning message

Closes https://github.com/api3dao/airseeker-v2/issues/114

LGTM, I'll keep .name in mind for the future

I think it's a neat trick and the benefit is that renaming refactor will also change the name of the test (describe block).


text:
Claim Swagger UI and Redoc

Checklist:

[ ] 遵循翻译排版和词汇要求。
[ ] 执行 tox -e docs，处理错误。
[ ] 检查文档预览，修复错别字和 Markdown 语法错误。

这里我昨天已经手动更新过了。

authors: Tridagger greyli

repo: apiflask/docs-zh


text:
Runnig crawler cause to restart the server

Hi,
I'm using puppeteercrawler as in this example https://sdk.apify.com/docs/examples/puppeteercrawler
it's running fine, but when it finishes it restart the project automatically causing to stop all other running services.
in nodemon, it displays this message
[nodemon] clean exit - waiting for changes before  restart
[nodemon] restarting due to changes...
[nodemon] starting `node app.js`

I used forever and pm2 and they did the same thing

It's just a hunch because we're not typically using nodemon or any other manager to keep the crawlers alive, but nodemon checks for changes in the filesystem to restart the process so perhaps try to turn this feature off or exclude apify_storage folder from its scope, because there are files being added to the folder, which may be triggering the restarts.

@mnmkng I need to run more than one crawler in parallel in my project, but when any one of them finished all other crawlers are stopped.
for nodemon, I did what you mentioned and tried other managers (forever,pm2) where there is no filesystem watcher

The SDK is not designed to run multiple crawlers from a single project folder, because they would use the same underlying storages such as RequestQueue. You can work around this by using named storages, such as:
await Apify.openRequestQueue('my-queue');

But note that those storages are not automatically cleared with apify run -p and having an existing queue with all requests in the handled folder can prevent a crawler from starting.
I'd be interested to know why you need to run multiple crawlers in the first place? A single crawler can crawl multiple domains and can run multiple browsers concurrently, so barring some edge cases, there should be no reason to use more than one instance of PuppeteerCrawler.

we have dozens of different websites each with a different set of settings and variable and would want to control the concurrency speed for each and run them individually based on a scheduler set for each website run, if there is an example of one crawler that is running different websites respecting the setting for each would be great, also any ideas regarding our use case would be awesome.

And for puppeteer queue I solved this problem by using named queue and ignored apify_storage file.

We actually solve this problem really well on our platform. When running on Apify, you would just create an actor with all common settings predefined and provide the individual settings as input parameters. A good example is the Web Scraper which accepts a lot of various configurations and you can save those as tasks and start them with a simple API call. We also have a plug&play Scheduler available. Feel free to check the source code too.
Locally, it's a bit more of a challenge, because you don't have the separate environments and distributed storages that our platform provides, but I think that you can get away with using named storages, just as you said. Just make sure to always clear them before re-use.
I'll close this because the original crawler restart issue is resolved, but feel free to continue conversation.

And for puppeteer queue I solved this problem by using named queue and ignored apify_storage file.

Could you please share your puppeteer code

authors: ahmedeldeeb25 mnmkng suheabkhan

repo: apify/apify-js


text:
Ignore Index columns from Primary Key map.

Added  i.indisprimary to the search clause. https://wiki.postgresql.org/wiki/Retrieve_primary_key_columns

Added Unit testcase to test this scenario and ensure it works. Without this fix, the Primary key test will fail.

+2 @gbrail give me the perms for this repo.
@sramamoorthy73 merge it for now

repo: apigee-labs/transicator


text:
Apigee -

Hi Team, @srinandan
In the apigee documentation here - you can see that sSLInfo info is a struct:
https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.environments.targetservers#TargetServer
Here you can see sSLInfo declared as a strut:
https://github.com/apigee/apigeecli/blob/main/internal/client/targetservers/targetservers.go#L46
But here you can see it passed as a string
https://github.com/apigee/apigeecli/blob/main/internal/client/targetservers/targetservers.go#L64
Which means calls to update the target server configuration are not working as expected.
Could you please help us here?

sslinfo is a boolean field. Please see [here]https://github.com/apigee/apigeecli/blob/main/cmd/targetservers/updatets.go#L35
Can you please paste the command you tried? That will help me reproduce the problem.

Hi @srinandan Thanks for you response as always
To add more details on what @m0xga has shared.
Our requirement is to use Truststore field in the target Server.
Agree, sslinfo is a boolean and if set to true it sets all these fields below this line
https://github.com/apigee/apigeecli/blob/main/internal/client/targetservers/targetservers.go#L99
However it looks like we are not setting Truststore in this and on that matter not even taking that as an input to this function.
I think if we will add that field that we will be golden here.

I got the problem and I have pushed a new release here. Unfortunately I wasn't able to try it and independently confirm the fix works. Can you please let me know if it worked?

Thank you kindly @srinandan we will get this tested

repo: apigee/apigeecli


text:
first attempt to export from API Gateway

This is a hastily-written exporter that creates API entries for each gateway in the currently-configured gcloud project. It uses gcloud to call the apigateway API (that could be replaced with direct calls). I've exported both OpenAPI and gRPC services and verified that exported results are read into the registry, but the protobuf-based specs aren't fully-resolved (they are missing common dependencies), so they won't be compilable with protoc without some additional work.
This is potentially all throwaway code, I just wanted to have something to show for API Gateway.
Usage: registry-connect discover apigateway gateways --output DIRECTORY where DIRECTORY is the directory to contain exported Registry YAML and API specs. This requires that gcloud be installed and configured to use a project that has some API Gateway instances to export.
By default it writes to gateway-export and here's what I get for a sample project with three gateways:
$ find gateway-export/
gateway-export/
gateway-export/timburks-test-shakes
gateway-export/timburks-test-shakes/info.yaml
gateway-export/timburks-test-shakes/shakes.proto
gateway-export/timburks-test-shakes/api_config.yaml
gateway-export/timburks-test-bookstore
gateway-export/timburks-test-bookstore/info.yaml
gateway-export/timburks-test-bookstore/bookstore.proto
gateway-export/timburks-test-bookstore/api_config.yaml
gateway-export/timburks-test-hello
gateway-export/timburks-test-hello/info.yaml
gateway-export/timburks-test-hello/openapi.yaml

$ cat gateway-export/timburks-test-shakes/info.yaml
apiVersion: apigeeregistry/v1
kind: API
metadata:
  name: timburks-test-shakes
  labels:
    provider: timburks-test
data:
  displayName: timburks-test gateway shakes
  description: Exported from API Gateway
  versions:
    - metadata:
        name: v1
      data:
        displayName: v1
        specs:
          - metadata:
              name: protos
            data:
              filename: protos.zip
              mimeType: application/x.proto+zip
  deployments:
    - metadata:
        name: gateway
      data:
        displayName: gateway
        endpointURI: https://shakes-8ez1hpbl.wl.gateway.dev

I'll follow up with a PR that sets some labels with more detail.

repo: apigee/registry-experimental


text:
Google Colab compatibility

I'm trying to speed up things by running it in Colab but I get this:

File "/usr/local/lib/python3.6/dist-packages/videocr/video.py", line 1
from future import annotations
^
SyntaxError: future feature annotations is not defined

Can you make it compatible with python 3.6 so it can be used in Google Colab with a GPU?
Thanks!

Yes, that would be great.
It is a fantastic idea and first work but the dev seems to have disappear. Did you find anything else working in google collab?

authors: Alqua NGamma


text:
How to get an interactive shell and send commands to docker and get the responses

Hello.
I want to get an interactive shell from my remote docker container to type commands and get back the responses.
I read the documentation and examples but I couldn't figure out how to do it.  Could someone please provide a sample code, for example a code snippet that creates and run an ubuntu container and then connect to this container to execute simple commands.
I think this code sample would be useful for people who are new to docker like me.
Thanks.

This Example Helped https://github.com/apocas/dockerode/blob/master/examples/run_stdin.js
But every letter is written two times in the screen.
for example ls command is converted to llss

This Link helped me to solve the duplicate letter problem.
https://stackoverflow.com/questions/24661774/createinterface-prints-double-in-terminal

I could not solve the duplication of letters.
When I use
readline.createInterface({ input: process.stdin, output: process.stdout, terminal: false })
mentioned in previous stackoverflow link I loose the terminal behavior like using tab and arrow keys.

@ehsanshekari
the following tyepscript code work for me
@apocas it will be usefull to share the following code in your docs or example it more helpfull than attach example
  public async interactiveShell(containerName: string) {
    const container = this.dockerApi.getContainer(
      containerName
    );

    const exec = await container.exec({
      Cmd: ['sh'],
      AttachStderr: true,
      AttachStdout: true,
      AttachStdin: true,
      Tty: true,
    });

    const http = await exec.start({stdin: true});
    const stream = http.output;

    (<any>process.stdin).setRawMode(true);
    stream.pipe(process.stdout);
    process.stdin.pipe(stream);

    await new Promise(resolve => {
      stream.on('end', resolve);
    });

    (<any>process.stdin).setRawMode(false);
    process.stdin.resume();

  }

This one seems tackled, going to close it.
Please feel free to submit a merge request with that example :)

authors: apocas ehsanshekari sanadHaj

repo: apocas/dockerode


text:
Better RxJava understanding/docs

I'm following the limited RxJava support docs https://github.com/apollographql/apollo-android#rxjava2-support
I don't quite understand why a StoreOperation maps to a Single and Calls and Queries map to Observables. IIUC a store operation is a hit to the local cache, whereas calls and queries are remote requests. What if I expect my remote request to return a single response, not a stream of responses? Should that not also be mapped to a Single?

The reason is that Queries will return several values: usually one for the cached response and one for the network response.

What if I only want a network response? I.e. if I know the value is not cached yet? Can I still use a Single?

Yes, you can use all the RxJava magic for that. Stuff like Observable.toSingle(), etc...

Closing this since the new docs are little better. This behavior is also documented in it's javadoc. Since there is no guarantee that it will return a Single object, the Return type cannot be a Single.
As Martin mentioned, RxJava has couple of operations to convert to Single type.

authors: martinbonnin tasomaniac tir38

repo: apollographql/apollo-android


text:
Collection of nested objects being mutated when IDs match

I'm making a query for an array of nested objects, basically like this:
[
  {
    // ... other values,
    id: 123
    subValue: {
       // ... other values,
       id: 345
      messedUpObject: {
        // ... other values,
        id: 0
      }
    }
  }
]

In this example, the parent object (id: 123) is fine, the subValue object is fine, but where the messedUpObject has the same id in separate parent objects, the properties are all set to the same value. For example, I could be expecting a result like this:
[
  {
  // ...parentObjects
    messedUpObject: {
      id: 0,
      name: 'Bob'
    },
  },
  {
  //... other parentObjects
    messedUpObject: {
      id: 0,
      name: 'Mary'
    }
  }
]

but in my response back I'm getting every messedUpObject with the name property set to 'Bob'.
While I understand that IDs should all be unique, why is Apollo/Graphql being opinionated about my schema? Especially when the parent objects contain unique IDs?
apollo-angular: 1.1.2
angular: 5.2.2

@patoncrispy I see that you've got two objects of the same type with the same ID but with different values on one key. Since they've got the same ID it should mean it's the same record but why they are different? Shouldn't they have different IDs instead?

It should, because ID means "this object is unique" and if it's unique and you return new object in mutation then you've got an information about what changed in it. Please read the documentation to understand why that's a thing.  https://www.apollographql.com/docs/angular/features/cache-updates.html#automatic-updates

authors: kamilkisiela patoncrispy

repo: apollographql/apollo-angular


text:
Make required mock fields nonoptional in convenience initializers

Makes the mock initialization parameters corresponding to nonull fields nonoptional. This allows the compiler to detect an invalid mock, rather than allowing an incomplete mock to cause an error at runtime.
Also fixes a bug in which the rendered type of a deeply nested mock field would be typed as required, even though it might be defined as optional.

@dwroth: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

Thank you for making a PR @dwroth, but the reason why all fields are optional on the mocks is because, even if a field on a type is non-null, it may not have been selected and fetched for any given operation. You should not be required to set values for fields if they are not selected in the operation that you are trying to mock.

Also fixes a bug in which the rendered type of a deeply nested mock field would be typed as required, even though it might be defined as optional.

I'm not sure what you are referring to here, and without a unit test as an example, I can't tell if this is expected behavior or not. If you still believe this to be a bug, lets talk about it further.

I see, that makes sense.  Thank you for clearing that up @AnthonyMDev .
As for the bug I was referring to (assuming I'm reading this code correctly):  consider the customScalarOptionalList defined in MockObjectTemplateTests.  It is an optional list of optional scalars.  Yet the output mock template has it typed as an optional list of non-optional scalars.

authors: AnthonyMDev apollo-cla dwroth

repo: apollographql/apollo-ios-dev


text:
Federation and local schema/query/resolvers

Hi, been experimenting with Apollo and Graphql (heard about it on Syntax and JAM stack radio). The federation example i've been trying to extend by having additional schema/query/resolvers at the gateway level. Is this possible? I have an existing bunch of microservices and a very small team so was thinking of merging the two approaches to get up and running quickly and slowly move to federated model.
Example code:
const { ApolloServer, gql } = require("apollo-server");
const { ApolloGateway } = require("@apollo/gateway");
const { makeExecutableSchema } = require("graphql-tools");

const typeDefs = gql`
  type Query {
    getPerson(id: Int!): Person
    getFilm(id: Int!): Film
  }

  type Film {
    title: String
    episode_id: Int
    opening_crawl: String
    director: String
    characters: [Person]
  }
  type Person {
    name: String
    height: String
    gender: String
    films: [Film]
  }
`;

const resolvers = {
  Film: {},
  Person: {},
  Query: {
    getPerson: async (_, { id }, ctx, info) => {
      const response = await fetch(`https://swapi.co/api/people/${id}/`);
      return response.json();
    },
    getFilm: async (_, { id }, context, info) => {
      const response = await fetch(`https://swapi.co/api/films/${id}/`);
      return response.json();
    },
  },
};

const schema = makeExecutableSchema({
  typeDefs,
  resolvers,
});

const gateway = new ApolloGateway({
  schema,
  serviceList: [
    { name: "accounts", url: "http://localhost:4001/graphql" },
    { name: "reviews", url: "http://localhost:4002/graphql" },
    { name: "products", url: "http://localhost:4003/graphql" },
    { name: "inventory", url: "http://localhost:4004/graphql" },
  ],
});

I've answered a similar question here - https://stackoverflow.com/a/61637093/2748290

@linguamachina many thanks for that.

authors: daveKoala linguamachina

repo: apollographql/federation-demo


text:
add react-dom as peer depency

TODO:

[ ] If this PR is a new feature, reference an issue where a consensus about the design was reached (not necessary for small changes)
[ ] Make sure all of the significant new logic is covered by tests
[ ] Rebase your changes on master so that they can be merged easily
[ ] Make sure all tests and linter rules pass
[x] Update CHANGELOG.md with your change
[ ] If this was a change that affects the external API, update the docs and post a link to the PR in the discussion

@koenpunt if I'm not mistaken people could use react-apollo anywhere they like, not only in the browser, so I'm not sure why we should add react-dom as a peer dependency?

since React 15.4 react-dom is no longer "secretly" included.
ref: https://github.com/facebook/react/releases/tag/v15.4.0

And since react-dom/server is required from server.ts, this causes errors.

Ah, I did not see that, thanks!
Can you sign the CLA?

What will this PR mean for using react-apollo in React Native? Will you need to install react-dom as a dependency to prevent NPM from complaining?

What will this PR mean for using react-apollo in React Native?

I am using react-apollo with React Native, and building fails without adding react-dom as a dependency due to the before mentioned require

Having to install react-dom as a dependency when using React Native isn't good though.

@migueloller don't you effectively already have to do that now if you use SSR? Or is SSR not a thing in react-native?
Since we only use renderToString, we could potentially use a pared down react-dom package if such a thing exists.

@helfer,
SSR is not a thing in React Native. The React team keeps the core React library separate from the different renderers (native, DOM/SSR, ART, etc.) so it might make sense to separate DOM/SSR logic from Apollo into a different package.
Perhaps there could be a pared down renderToString out there somewhere that doesn't include all of the shadow DOM diffing logic that ReactDOM.render needs and simply traverses the component tree and renders it. I haven't come across it though.

@migueloller we have discussed moving the main logic of this renderer out of this package. For now, I think we should merge this. Up until 15.4 RN builds got react-dom anyway.
I think in a future release we should remove the react-dom integration for a new package or just remove the render to string part. This would also allow this library to potentially be used with react-like renderers (i.e inferno and preact)

@koenpunt could you update the changelog?

@jbaxleyiii done.

@koenpunt sorry this took so long to merge!

authors: helfer jbaxleyiii koenpunt migueloller

repo: apollostack/react-apollo

license: mit


text:
Create Blog “2018-03-13-spicy”

Automatically generated by Netlify CMS

Deploy preview for practical-ramanujan-39b206 ready!
Built with commit 92086ac18edb09779e665b352a58ea09235ef960
https://deploy-preview-12--practical-ramanujan-39b206.netlify.com

repo: aponder-celartem/verbose-bassoon


text:
fixed ipam host-local IP json tag

Signed-off-by: André Martins aanm90@gmail.com

Thanks!

authors: aanm steveeJ

repo: appc/cni


text:
Pod Volumes could be clearer

What happens if I spec source for an "empty"?
Can we spec this whole block more as a conditional?  "if kind is 'empty' ... fields; if kind is 'host' ... fields".

Agreed, this can be tackled along with #183

Will address in #183

authors: jonboulle thockin

repo: appc/spec


text:
"name" and "value" keys unnecessarily verbose?

Hi again!
Is there any particular reason why the "name" and "value" keys are used for labels, annotations, isolators, eventHandlers and environment variable lists? If those things were objects themselves, instead of lists, the ACI image schema would be much simpler and less verbose.
For instance, if you made the lists into objects for the above mentioned attributes of the image schema, you would go from this (from the examples):
{
    "acKind": "ImageManifest",
    "acVersion": "0.7.0",
    "name": "example.com/reduce-worker",
    "labels": [
        {
            "name": "version",
            "value": "1.0.0"
        },
        {
            "name": "arch",
            "value": "amd64"
        },
        {
            "name": "os",
            "value": "linux"
        }
    ],
    "app": {
        "exec": [
            "/usr/bin/reduce-worker",
            "--quiet"
        ],
        "user": "100",
        "group": "300",
        "supplementaryGids": [
                400,
                500
        ],
        "eventHandlers": [
            {
                "exec": [
                    "/usr/bin/data-downloader"
                ],
                "name": "pre-start"
            },
            {
                "exec": [
                    "/usr/bin/deregister-worker",
                    "--verbose"
                ],
                "name": "post-stop"
            }
        ],
        "workingDirectory": "/opt/work",
        "environment": [
            {
                "name": "REDUCE_WORKER_DEBUG",
                "value": "true"
            }
        ],
        "isolators": [
            {
                "name": "resource/cpu",
                "value": {
                    "request": "250m",
                    "limit": "500m"
                }
            },
            {
                "name": "resource/memory",
                "value": {
                    "request": "1G",
                    "limit": "2G"
                }
            },
            {
                "name": "os/linux/capabilities-retain-set",
                "value": {
                    "set": ["CAP_NET_BIND_SERVICE"]
                }
            }
        ],
        "mountPoints": [
            {
                "name": "work",
                "path": "/var/lib/work",
                "readOnly": false
            }
        ],
        "ports": [
            {
                "name": "health",
                "port": 4000,
                "protocol": "tcp",
                "socketActivated": true
            },
            {
                "name": "ftp-data",
                "port": 20000,
                "count": 1000,
                "protocol": "tcp"
            }
        ]
    },
    "dependencies": [
        {
            "imageName": "example.com/reduce-worker-base",
            "imageID": "sha512-...",
            "labels": [
                {
                    "name": "os",
                    "value": "linux"
                },
                {
                    "name": "env",
                    "value": "canary"
                }
            ],
            "size": 22017258
        }
    ],
    "pathWhitelist": [
        "/etc/ca/example.com/crt",
        "/usr/bin/map-reduce-worker",
        "/opt/libs/reduce-toolkit.so",
        "/etc/reduce-worker.conf",
        "/etc/systemd/system/"
    ],
    "annotations": [
        {
            "name": "authors",
            "value": "Carly Container <carly@example.com>, Nat Network <[nat@example.com](mailto:nat@example.com)>"
        },
        {
            "name": "created",
            "value": "2014-10-27T19:32:27.67021798Z"
        },
        {
            "name": "documentation",
            "value": "https://example.com/docs"
        },
        {
            "name": "homepage",
            "value": "https://example.com"
        }
    ]
}

to this:
{
    "acKind": "ImageManifest",
    "acVersion": "0.7.0",
    "name": "example.com/reduce-worker",
    "labels": {
        "version": "1.0.0",
        "arch": "amd64",
        "os": "linux"
    },
    "app": {
        "exec": [
            "/usr/bin/reduce-worker",
            "--quiet"
        ],
        "user": "100",
        "group": "300",
        "supplementaryGids": [
                400,
                500
        ],
        "eventHandlers": {
            "pre-start": {
                "exec": [
                    "/usr/bin/data-downloader"
                ]
            },
            "post-stop": {
                "exec": [
                    "/usr/bin/deregister-worker",
                    "--verbose"
                ]
            }
        },
        "workingDirectory": "/opt/work",
        "environment": {
            "REDUCE_WORKER_DEBUG": "true"
        },
        "isolators": {
            "resource/cpu": {
                    "request": "250m",
                    "limit": "500m"
            },
            "resource/memory": {
                    "request": "1G",
                    "limit": "2G"
            },
            "os/linux/capabilities-retain-set": {
                "set": ["CAP_NET_BIND_SERVICE"]
            }
        },
        "mountPoints": {
            "work": {
                "path": "/var/lib/work",
                "readOnly": false
            }
        },
        "ports": {
            "health": {
                "port": 4000,
                "protocol": "tcp",
                "socketActivated": true
            },
            "ftp-data": {
                "port": 20000,
                "count": 1000,
                "protocol": "tcp"
            }
        }
    },
    "dependencies": [
        {
            "imageName": "example.com/reduce-worker-base",
            "imageID": "sha512-...",
            "labels": {
                "os": "linux",
                "env": "canary"
            },
            "size": 22017258
        }
    ],
    "pathWhitelist": [
        "/etc/ca/example.com/crt",
        "/usr/bin/map-reduce-worker",
        "/opt/libs/reduce-toolkit.so",
        "/etc/reduce-worker.conf",
        "/etc/systemd/system/"
    ],
    "annotations": {
        "authors": "Carly Container <carly@example.com>, Nat Network <[nat@example.com](mailto:nat@example.com)>",
        "created": "2014-10-27T19:32:27.67021798Z",
        "documentation": "https://example.com/docs",
        "homepage": "https://example.com"
    }
}

The latter doesn't lose any information, and is significantly less verbose (and IMHO easier to read).
Thoughts?
Best,
-jay

Hmm, this has been discussed before in #58, #62, #64, and #84 and we landed on the more verbose format. To reiterate here:
It maintains that field names on the left are schema, values on the right are user values. Behavior during duplicate JSON object field names are not part of the JSON spec and may be handled differently based on the library being used...but generally an ill-formed manifest will have duplicate errors swallowed during JSON parsing. Some label names are not valid JSON object member names.

OK, that's good information, thank you. I guess I don't really see why AppC would use JSON as its file format and then allow "label names [to not be] valid JSON object member names." That doesn't make a whole lot of sense to me. Why bother using JSON at all, then, if you're just going to override what JSON means with the parser.go implementation? Or, put another way, what does not conforming to the JSON spec give AppC?

I guess I don't really see why AppC would use JSON as its file format and then allow "label names [to not be] valid JSON object member names." That doesn't make a whole lot of sense to me. Why bother using JSON at all, then, if you're just going to override what JSON means with the parser.go implementation? Or, put another way, what does not conforming to the JSON spec give AppC?

I'm a bit confused by @cdaylward's point here, as I don't know of cases where label names are invalid member names.
As justification for this schema I would lean more on his other points with respect to the field name/user value split.

authors: cdaylward jaypipes jonboulle


text:
Updated: seafile-client 7.0.6

$notices:
- Updated `installers.host`
- Updated `installers.segments`

e4c52246-8dda-4650-9465-25a615f6bf98

Newer version of seafile-client (7.0.7) is now available in master. 71c5d694964fe676dff092c2aac93c5f38264455


text:
Prize and PrizeList React components

Requirements

[ ] Two components PrizeItem and PrizeList where PrizeList may contain multiple PrizeItem(s)
[ ] Should be styled as shown in specks

I am doing this
Regards

Go ahead :+1:

I have submitted the pull request

@amolskh
Final fixes:

[ ] Can we reuse TaggedValue and/or TaggedValueList components for these two components?

Yes we can use ..Do you mean currently PrizeList component should referred internally to taggedList component
Please confirm..

Didn't get your point @amolskh. We would still have PrizeItem and PrizeItemList components, however, they would delegate actual rendering to TaggedValue and TaggedValueList components respectively. We can either inherit TaggedValue in PrizeItem and TaggedValueList in PrizeItemList or just encapsulate TaggedValue in PrizeItem and TaggedValueList in PrizeList. It would be more clear, which one to use, when you try to implement one of them ways. Personally, I would prefer the inheritance way.

@amolskh Do you need further clarification for final fix?

Sorry for the delay.. I have made PR please review and merge

authors: amolskh vikasrohit

repo: appirio-tech/react-components


text:
Fix function spacing

Add a space before opening parenthesis in function declarations. Once this is in I'll update the eslint config to add the rule to check this.

👍

authors: imurchie jlipps

repo: appium/appium-ios-driver


text:
Make sure we return something useful from getting the date

If we can't parse the date string from idevicedate, return something useful (i.e., the output itself).
See https://github.com/appium/appium/issues/7835

Published in appium-ios-driver@1.27.5