[WIP][SPARK-32138] Drop Python 2.7, 3.4 and 3.5

What changes were proposed in this pull request?
TBD
Why are the changes needed?
TBD
Does this PR introduce any user-facing change?
TBD
How was this patch tested?
TBD

I'm supporting @HyukjinKwon 's idea, but cc @gatorsmile and @marmbrus since they wanted to keep the deprecated features forever if there is no big burden.

Also, cc @rxin

Test build #124645 has started for PR 28957 at commit 3efa521.

Test build #124645 has finished for PR 28957 at commit 3efa521.

This patch fails Python 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/124645/
Test FAILed.

Merged build finished. Test PASSed.

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

Thanks for working on this! @fokko do we have a rough idea what % of general users are running Python 3.6+?

My pleasure @holdenk
I ran a query against the public dataset of Google. They have a dataset that contains all the public pypi downloads:
SELECT
  EXTRACT(YEAR FROM timestamp) AS year,
  EXTRACT(MONTH FROM timestamp) AS month,
  SAFE.SUBSTR(details.python, 0, 3) AS python_version,
  COUNT(*) AS num_downloads
FROM `the-psf.pypi.downloads*`
WHERE file.project = 'pyspark'
AND SAFE.SUBSTR(details.python, 0, 3) IS NOT NULL
GROUP BY
  EXTRACT(YEAR FROM timestamp),
  EXTRACT(MONTH FROM timestamp),
  SAFE.SUBSTR(details.python, 0, 3)

This gives us the following per month:

We can see that the majority uses 3.7 and 3.6. However, there is still a share of 3.5 and 2.7.
If we look at the proportional share of people who'm using a compatible version:
SELECT
  EXTRACT(YEAR FROM timestamp) AS year,
  EXTRACT(MONTH FROM timestamp) AS month,
  if(SAFE.SUBSTR(details.python, 0, 3) >= '3.6', 'ok', 'not_ok') as OK,
  COUNT(*) AS num_downloads
FROM `the-psf.pypi.downloads*`
WHERE file.project = 'pyspark'
AND SAFE.SUBSTR(details.python, 0, 3) IS NOT NULL
GROUP BY
  EXTRACT(YEAR FROM timestamp),
  EXTRACT(MONTH FROM timestamp),
  if(SAFE.SUBSTR(details.python, 0, 3) >= '3.6', 'ok', 'not_ok')

Then the majority is ok:

The next question would be if Python <3.6 users are on 3.0 or on 2.x. My guess would be the latter, so we're (mostly) safe deprecating the old versions of Python.

Thanks @Fokko for the investigation here.

Wow, nice investigation, @Fokko ! Thanks.

Test build #124750 has started for PR 28957 at commit dd288ca.

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

Test build #124750 has finished for PR 28957 at commit dd288ca.

This patch fails Python 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/124750/
Test FAILed.

@HyukjinKwon . Did you get a chance to get a feedback from @marmbrus and @gatorsmile ?

cc @mateiz and @rxin

Nope, I am waiting for more feedback - I usually share anything up in OSS side. I was just assuming it's good enough to go given @Fokko's investigation at https://github.com/apache/spark/pull/28957#issuecomment-652022449.

I will send an email to dev list to confirm. I think that's faster.

Test build #124846 has started for PR 28957 at commit d74aa53.

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

Merged build finished. Test PASSed.

Test build #124846 has finished for PR 28957 at commit d74aa53.

This patch fails build dependency 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/124846/
Test FAILed.

retest this please

Test build #124848 has started for PR 28957 at commit d74aa53.

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

Test build #124848 has finished for PR 28957 at commit d74aa53.

This patch fails build dependency 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/124848/
Test FAILed.

retest this please

Test build #124849 has started for PR 28957 at commit d74aa53.

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

Test build #124849 has finished for PR 28957 at commit d74aa53.

This patch fails build dependency 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/124849/
Test FAILed.

retest this please

Test build #124853 has started for PR 28957 at commit d74aa53.

Test build #124853 has finished for PR 28957 at commit d74aa53.

This patch fails build dependency 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/124853/
Test FAILed.

Merged build finished. Test PASSed.

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

retest this please

Test build #124855 has started for PR 28957 at commit d74aa53.

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

Test build #124855 has finished for PR 28957 at commit d74aa53.

This patch fails build dependency 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/124855/
Test FAILed.

retest this please

Test build #124856 has started for PR 28957 at commit d74aa53.

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

Test build #124856 has finished for PR 28957 at commit d74aa53.

This patch fails build dependency 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/124856/
Test FAILed.

retest this please

Test build #124857 has started for PR 28957 at commit d74aa53.

retest this please

retest this please

retest this please

Test build #124857 has finished for PR 28957 at commit d74aa53.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build finished. Test FAILed.

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

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

Test build #124858 has started for PR 28957 at commit d74aa53.

Test build #124858 has finished for PR 28957 at commit d74aa53.

This patch fails build dependency 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/124858/
Test FAILed.

Test build #124861 has started for PR 28957 at commit 5a68bc3.

Test build #124861 has finished for PR 28957 at commit 5a68bc3.

This patch fails build dependency 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/124861/
Test FAILed.

Merged build finished. Test PASSed.

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

Test build #124862 has started for PR 28957 at commit bb5cfa3.

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

Test build #124862 has finished for PR 28957 at commit bb5cfa3.

This patch fails build dependency 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/124862/
Test FAILed.

retest this please

Test build #124909 has started for PR 28957 at commit bb5cfa3.

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

Test build #124909 has finished for PR 28957 at commit bb5cfa3.

This patch fails build dependency 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/124909/
Test FAILed.

retest this please

Test build #124912 has started for PR 28957 at commit bb5cfa3.

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

Test build #124912 has finished for PR 28957 at commit bb5cfa3.

This patch fails build dependency 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/124912/
Test FAILed.

retest this please

Test build #124940 has started for PR 28957 at commit 9ec81f2.

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

Test build #124940 has finished for PR 28957 at commit 9ec81f2.

This patch fails build dependency 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/124940/
Test FAILed.

retest this please

Test build #124986 has started for PR 28957 at commit 9ec81f2.

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

Test build #124986 has finished for PR 28957 at commit 9ec81f2.

This patch fails build dependency 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/124986/
Test FAILed.

Test build #125004 has started for PR 28957 at commit 646149f.

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

Merged build finished. Test PASSed.

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

Test build #125007 has started for PR 28957 at commit 92307e9.

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

Test build #125012 has started for PR 28957 at commit 63c6259.

Test build #125004 has finished for PR 28957 at commit 646149f.

This patch fails to generate documentation.
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/125004/
Test FAILed.

Merged build finished. Test FAILed.

Test build #125007 has finished for PR 28957 at commit 92307e9.

This patch fails to generate documentation.
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/125007/
Test FAILed.

retest this please

Test build #125023 has started for PR 28957 at commit 63c6259.

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

Test build #125012 has finished for PR 28957 at commit 63c6259.

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

Test build #125023 has finished for PR 28957 at commit 63c6259.

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

Merged build finished. Test FAILed.

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

Merged build finished. Test FAILed.

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

retest this please

Test build #125052 has started for PR 28957 at commit 63c6259.

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

Test build #125052 has finished for PR 28957 at commit 63c6259.

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

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

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

Test build #125084 has started for PR 28957 at commit 63c6259.

Test build #125084 has finished for PR 28957 at commit 63c6259.

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

Merged build finished. Test FAILed.

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

retest this please

Test build #125155 has started for PR 28957 at commit 63c6259.

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

Test build #125155 has finished for PR 28957 at commit 63c6259.

This patch fails to generate documentation.
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/125155/
Test FAILed.

retest this please

Test build #125157 has started for PR 28957 at commit 63c6259.

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

Test build #125157 has finished for PR 28957 at commit 63c6259.

This patch fails to generate documentation.
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/125157/
Test FAILed.

Merged build finished. Test PASSed.

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

retest this please

Test build #125457 has started for PR 28957 at commit de665aa.

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

Test build #125457 has finished for PR 28957 at commit de665aa.

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

Merged build finished. Test FAILed.

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

Test build #125470 has started for PR 28957 at commit 5f6ba37.

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

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

retest this please

Test build #125527 has started for PR 28957 at commit 5f6ba37.

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

Test build #125527 has finished for PR 28957 at commit 5f6ba37.

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

cc @BryanCutler, @ueshin, @holdenk, @dongjoon-hyun, @viirya, @srowen, this should be ready for a review.

Looks good overall.

I commented and filed two JIRAs SPARK-32278 and SPARK-32279 for Jenkins env. cc @shaneknapp FYI.
Currently, PyPy 3 is not being tested in Jenkins, and PySpark documentation build via Sphinx is being skipped because Python 3 does not have Sphinx.
These will be tested via Github Actions for now via #29057.

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

Test build #125663 has started for PR 28957 at commit ec42492.

Test build #125663 has finished for PR 28957 at commit ec42492.

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

Merged build finished. Test FAILed.

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

I'll merge GitHub actions one first, and fix the conflicts here

I merged GitHub Action PR. Please rebase this to the master. Thanks, @HyukjinKwon .

Sure, thanks @dongjoon-hyun

Test build #125739 has started for PR 28957 at commit 9e8100f.

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

Test build #125739 has finished for PR 28957 at commit 9e8100f.

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

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

Test build #125755 has started for PR 28957 at commit 5c27ea8.

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

Test build #125765 has started for PR 28957 at commit f2356c8.

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

Test build #125755 has finished for PR 28957 at commit 5c27ea8.

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

Merged build finished. Test FAILed.

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

Test build #125765 has finished for PR 28957 at commit f2356c8.

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

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

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

Test build #125774 has started for PR 28957 at commit f2356c8.

Test build #125774 has finished for PR 28957 at commit f2356c8.

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

Merged build finished. Test FAILed.

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

retest this please

Test build #125786 has started for PR 28957 at commit f2356c8.

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

Test build #125786 has finished for PR 28957 at commit f2356c8.

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

I am merging it to master. Thank you guys for reviewing this.

Merged to master.

Thanks for doing this, awesome work :)

Cool stuff, thanks for the work @HyukjinKwon

Great! Thank you always for leading PySpark part (in addition to all the other Spark module), @HyukjinKwon !


Missing Joypad Button Index label.

Godot version: 3.1.1.stable.official

OS/device including version: Linux Mint 19.1 Cinnamon

Issue description:

When configuring input maps the buttons 10 and 11 are only named for Nintendo controllers, while DS4 controllers also use the same index's.
The SHARE(left) button is the equivalent of button_index 10
The OPTIONS(right) button is the equivalent of button_index 11
Steps to reproduce:
NA
Minimal reproduction project:
NA

There are several different names for the two central buttons on game controllers: "Share/Options" for the ps4, "View/Menu" for the Xbox One, and "Back/Start" for the Xbox 360, etc. Although it seems that the name "Select/Start" is generally understood since it dates way back (NES controller, maybe even before that).
Now I think it would be nice if there were the specific names for each type of controller but I don't know which ones should be included... Just the Xbox One and PS4? Or also the PS3 and Xbox 360?

There are already names for most of them so it feels like the start /
select are missing.
On Mon, Jul 1, 2019, 00:14 daniel-luper<EMAIL_ADDRESS>wrote:

There are several different names for the two central buttons on game
controllers: "Share/Options" for the ps4, "View/Menu" for the Xbox One, and
"Back/Start" for the Xbox 360, etc. Although it seems that the name
"Select/Start" is generally understood since it dates way back (NES
controller, maybe even before that).
Now I think it would be nice if there were the specific names for each
type of controller but I don't know which ones should be included... Just
the Xbox One and PS4? Or also the PS3 and Xbox 360?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/30163?email_source=notifications&email_token=AF2PG3DOA3PXOXW4EVUOZODP5EV2RA5CNFSM4H4HCJD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY4UZ5A#issuecomment-507071732,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF2PG3GF6HRQ65GE6TXHSDTP5EV2RANCNFSM4H4HCJDQ
.

Start and select are already there

Sorry. I mean it feels like Options / Share is missing.
On Mon, Jul 1, 2019, 11:55 daniel-luper<EMAIL_ADDRESS>wrote:

[image: image]
https://user-images.githubusercontent.com/50499124/60427341-69240200-9bee-11e9-9bc4-183441d449ca.png
Start and select are already there
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/30163?email_source=notifications&email_token=AF2PG3B6LEELFQISFIRU5PTP5HICFA5CNFSM4H4HCJD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY5TXVY#issuecomment-507198423,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF2PG3CZWMHCRRNPSN3OWBLP5HICFANCNFSM4H4HCJDQ
.

OK how about this? Legit just two strings to modify xD

Yes, something like that! Tried searching for them but couldn't find them.
man. 1. jul. 2019 kl. 18:04 skrev daniel-luper<EMAIL_ADDRESS>
[image: share-options]
https://user-images.githubusercontent.com/50499124/60450540-fd5b8c80-9c21-11e9-8dc8-646531f96fad.png
OK how about this? Legit just two strings to modify xD
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/30163?email_source=notifications&email_token=AF2PG3AZNQLO7J7HV5ALPLDP5ITJPA5CNFSM4H4HCJD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6TFHI#issuecomment-507327133,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF2PG3GFZJYFFHXVGZXP2I3P5ITJPANCNFSM4H4HCJDQ
.


⚠ ClamAV has degraded performance

In 4464e91, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in ebd27b1.


ROCm enable depthwise_conv_ops_test

the corresponding unit test is whitelisted...can you check if it passes in your local build, and if it does please remove it from the whitelist as well :)

@jeffdaily even the CI test result is a success I'm still closing this PR as the test itself is in the whitelist after all. please help address the comments from me and @deven-amd and reopen it.

Removing //tensorflow/python/kernel_tests:depthwise_conv_op_test (tensorflow/python/kernel_tests/depthwise_conv_op_test.py) from the whitelist failed.  That test is trying to use the kernel DepthwiseConv2dNative labeled cudnn_grouped_convolution from tensorflow/core/kernels/depthwise_conv_op.cc line 489.
The test that this PR is enabling is //tensorflow/core/kernels:depthwise_conv_ops_test.  The test is also failing, but because tensorflow/core/kernels/ops_testutil.cc returns with error Requesting GPU on binary compiled without GOOGLE_CUDA.  See https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/blob/develop-upstream/tensorflow/core/kernels/ops_testutil.cc.  Should we ROCm enable this file?

I'll answer my own question.  Enabling ROCm in the above file would also require hipMallocManaged.  Since we don't support hipMallocManaged this test will never work.  Best to leave this PR closed for good.
In other news depthwise conv will be supported in MIOpen 1.5, so we should revisit the depthwise kernel and whitelist again after that release.


Error during installation at step cache:clear

Hello.
First sorry for my English.
I'm trying to start my first project with RoadRunner using Symfony. And when I'm trying to install this bundle and then do any other installs with composer I'm getting an error in FluffyDiscordRoadRunnerExtension.php line 51 that saying I'm trying to auto register RoadRunner KV cache without installing the corresponding package.
To get the error I did nothing more than:

symfony new rr-test && cd rr-test
composer require spiral/roadrunner-cli
./vendor/bin/rr get-binary
Answer yes to the proposal to create default ".rr.yaml" configuration
composer require fluffydiscord/roadrunner-symfony-bundle
Get [KO] at cache:clear

Later I found that it is happening because of kv: configuration lines presence in the received default .rr.yaml and the error is gone when I delete them. But is it such important to get the lines removed at first place from the default configuration before start using this runtime? Or should I just not take this bundle for my first project with RR?

@TrueXakeP hello, the behaviour is expected
This package does not rely on KV cache, but auto-registers the cache adapters if it finds them defined in .rr.yaml.
You are free to either:

Install the KV package as exception explains
Remove KV definition from .rr.yaml
Disable auto cache registration, as explained in README in fluffy_discord_road_runner.yaml

fluffy_discord_road_runner:
  kv:
    auto_register: false

I recommend reading README explaining important things about this package at least once, to be aware what it can do or what are it's or symfony limitations.
I would be happy if you continue using my bundle and report back any issues you find (I am using it in all my projects, but there still might be things to be solved)

I apologize. Apparently I didn't read the README carefully enough. I'll be more careful in the future.


Damm Looking !!!

Can anyone help me to make a better UI for this Utility

i can work on the issue, pls sent me now!!!!!! thanks you so much

I believe I can improve this UI. Can you assign this for me?

Are you both the same guy 🤔 ?

Are you both the same guy 🤔 ? @LieuMai @ndmtuan

Haha, no sir, but we have same teacher I guest. We are studying how to contribute a opensource project. So this is our practice exercise.
I will be preciate if you can give us a try!!! ^_^

Issue assigned @LieuMai

You both can give it a try
@LieuMai
@ndmtuan
Best of Luck 👍

Would you like to style the red part too?  I found that demo can fetch data into the screen, I notice that I can't fetch data.

Would you like to style the red part too? ---> YES.
I found that demo can fetch data into the screen, but in source code I notice that I can't fetch data. --->
Step 1: Make a file with name .env in root folder (where .gitignore is present).
Step 2: Copy and Paste  REACT_APP_GITHUB_API = "https://api.github.com/users/" in .env file and save it.
Step 3: Do npm start again.
@LieuMai

Let me know it worked or not !!
@LieuMai

Let me know it worked or not !!
@LieuMai

It worked. Thank you, sir!

@garg-madhur-garg  I created a pull request. Please check and review if you like it or not. I will improve it.

If you want then you can make this page responsive.
And I think instead of splitting you can Capitalize the letters😊
And any other suggestions are always welcome !!

I am merging your PR,
You can continue your work on above mention points 👍
@LieuMai

Are you working on this ??
@LieuMai

@garg-madhur-garg The new design is done but it isn't responsive. I will create a pull request if you need it now. I'm so sorry but I couldn't comeback in the next two weeks. You can assign this issue for other people. When I completed the responsive part, I will create a pull request.

ok, you can create a pull request whenever your work is done
@LieuMai


Make the Coveralls badge in the README work

Description
Update Coveralls URIs in README.md so to get the badge working.
Use case
Our Coveralls badge as it is keeps saying "unknown" because it doesn't specify the branch in the URI, which apparently is necessary in case of Coveralls (and recommended for Travis as well). Moreover, the URI itself might be outdated.
Benefits
Actually get the badge to work.
Possible Drawbacks
Keeping it working for release branches will require updating the README as part of the release procedure.
Testing
Have you added/modified unit tests to test the changes?
No.
If so, do the tests pass/fail?
N/A
Have you run the entire test suite and no regression was detected?
No, this is a change to documentation - and a quantitative one at that.

Actually the ?branch=master at line 7 is not needed and is perhaps best removed.
That way there is only one place to update the branch at branching and the link always stays the same.

Coverage remained the same at 81.455% when pulling 54cc2af23b4d7403c70ebeac4c53a448b1cbc704 on bugfix/readme_badge_uris_master into b687ee4d3b524bef8832d0d8b20c4c3279aaf631 on master.


KAFKA-14299: Avoid busy polling in state updater

The state updater can enter a busy polling loop if it only updates
standby tasks. We need to use the user-provided poll-time to update
always when using the state updater, since the only other place where
the state update blocks (inside waitIfAllChangelogsCompletelyRead)
is also not blocking if there is at least one standby task.
The change is tested by a unit test. We will add an integration test
once this code path is more stable.
Committer Checklist (excluded from commit message)

[x] Verify design and implementation
[x] Verify test coverage and CI build status
[x] Verify documentation (including upgrade notes)

@cadonna Can you have a look?

I restarted the builds. Once the build results are acceptable, I will merge the PR.

Build failures are unrelated:
Build / JDK 11 and Scala 2.13 / kafka.admin.LeaderElectionCommandTest.[2] Type=Raft-CoReside, Name=testAllTopicPartition, MetadataVersion=3.3-IV3, Security=PLAINTEXT
Build / JDK 17 and Scala 2.13 / org.apache.kafka.connect.mirror.integration.MirrorConnectorsIntegrationSSLTest.testReplication()
Build / JDK 17 and Scala 2.13 / kafka.api.TransactionsExpirationTest.testTransactionAfterProducerIdExpires(String).quorum=kraft
Build / JDK 17 and Scala 2.13 / org.apache.kafka.trogdor.coordinator.CoordinatorTest.testTaskRequestWithOldStartMsGetsUpdated()


Time recorded is in minutes and not hours

The time which is punched is recorded in minutes and not hours. It would be useful if time recorded is in hours and not minutes

Not sure what you mean. Please elaborate?


Add generic schema validation for tests

Making tests right now is a more error-prone process than it could be because we don’t have any generic tools to validating that an output record matches our expected schema. We should really have a helper here so that most tests can focus more on particular and narrow.
For example, I’m thinking we should have something that lets us write a test like:
describe("Washington DoH API", () => {
  it.nock("should correctly format results", async () => {
    const result = await checkAvailability(() => {}, { states: "WA" });

    // This line is what I'm talking about.
    expect(result).toMatchSchema(locationRecordSchema);
  });

  // ...then other tests can provide more contrived data and test issues in specific fields, etc.

Instead of stuff like: https://github.com/usdigitalresponse/univaf/blob/17878bff1e01d31d8f33dfa7f9b92419b2532060/loader/test/wa-doh.test.js#L16-L86
We can probably use AJV for this and borrow some of the schema code from server/src/validation.ts.

This was done in #437.


cannot run C compiled programs

11:48 $ rbenv install
ruby-build: use openssl from homebrew
Downloading ruby-2.3.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.3/ruby-2.3.1.tar.bz2
Installing ruby-2.3.1...
ruby-build: use readline from homebrew

BUILD FAILED (OS X 10.12.5 using ruby-build 20170523)

Inspect or clean up the working tree at /var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20170609114818.92413
Results logged to /var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20170609114818.92413.log

Last 10 log lines:
checking build system type... x86_64-apple-darwin16.6.0
checking host system type... x86_64-apple-darwin16.6.0
checking target system type... x86_64-apple-darwin16.6.0
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in `/var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20170609114818.92413/ruby-2.3.1':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details

11:49 $ cat /var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20170609114818.92413.log
/var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20170609114818.92413 ~/Projects/locomote/itinerary
/var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20170609114818.92413/ruby-2.3.1 /var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20170609114818.92413 ~/Projects/locomote/itinerary
checking for ruby... /usr/bin/ruby
config.guess already exists
config.sub already exists
checking build system type... x86_64-apple-darwin16.6.0
checking host system type... x86_64-apple-darwin16.6.0
checking target system type... x86_64-apple-darwin16.6.0
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in `/var/folders/r2/6pxx62xx727c7_h4qp6zrpxw0000gn/T/ruby-build.20170609114818.92413/ruby-2.3.1':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details

11:50 $ brew doctor
Your system is ready to brew.

Tried to re-install xcode tools, rbenv, ruby-build, same result.

Ok, reboot helped

Im with the same issue. Reboot don't work form me.


Update Alfred to 2.7.1

The zipfile for 2.5.1 has been removed and is no longer accessible (url returns 404).
I've forked the puppet-alfred repo to update this and opened a PR, but it might be a while until it gets merged.
Until then, use alfred from my fork.

It shouldn't be necessary to fork the module as alfred is already a parameterised class which only has 2.5.1 as the default. Try adding alfred::version: 2.7.1 to hiera/common.yaml

aha, thanks Sam, I'll give that a whirl

that works :-)


Webhook Registry: Ensuring that the response body is always a Hash, even if ShopifyAPI.Context.response_as_struct is true.

Fixes https://github.com/Shopify/shopify-api-ruby/issues/1311
ensuring that the response body is always a Hash, even if ShopifyAPI.Context.response_as_struct is true.
Description
Had to add a Utility (ShopifyAPI::Utils::OstructHashUtils) to handle the conversion since a simple .to_h and even JSON.parse(response.body.to_json) did not work as expected (nested Keys and Array handling failed).
How has this been tested?
Wrote new Specs to test the registry process with ShopifyAPI::Context.response_as_struct = true
Checklist:

[x] My commit message follow the pattern described in here
[x] I have performed a self-review of my own code.
[x] I have added tests that prove my fix is effective or that my feature works.
[ ] I have updated the project documentation.
[ ] I have added a changelog line.

@DaveEshopGuide Thank you for this fix!
Could you add a post to the CHANGELOG.md and then this should be good to go!


Learn How to Talk About a Typical Workday and Tasks - Task 37 & 45 - typing cafés

Describe the bug
Task 37 requires typing cafés in one of the blanks. This can be problematic due to the é letter, which might not be present in the used keyboard layout.
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e2c02a685f4ec9ec951ff.md
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/21-a2-english-for-developers/learn-how-to-talk-about-a-typical-workday-and-tasks/657e3228f9f24007a7d59779.md
Expected behavior
I don't want to say to use completely different word for the fill the blank, as at some point there might be no other choice. There could be some kind way to ease up procuring of the letter in question, for example including it in the feedback, so it can be copied.

Hi @gikf I would love to work on this. If someone could point me in the right direction, that would be amazing!

Hi @shivasaikrishnagadeela,
Thank you for being eager to contribute.
This issue has not been triaged yet. Feel free to share your insights and ideas on the matter. However as far as the code contributing, take a look at the issues with help wanted label.
Please make sure you read our guidelines for contributing, we prioritize contributors following the instructions in our guides. Join us in our chat room or the forum if you need help contributing, our moderators will guide you through this.
Thank you and happy coding.

Yes, I think in both of those challenges we can update the "Don't forget the stress mark." in the feedback to:
"Don't forget the stress mark (é)."

"Don't forget the stress mark (é)."

I will open the issue to contribution with this as the solution


⚠ AGEG website (redirect) has degraded performance

In a7224b5, AGEG website (redirect) (https://ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 2519 ms

Resolved: AGEG website (redirect) performance has improved in ccde54a.


fix(carousel): fix animation direction

Properly fix the animation direction of the slides

Plunker in action here.
This fixes #4087.

Now it is a :+1:


Patterns

here's my write up for a-z and mini hub

The build is failing because there needs to be an empty new line at the end of the main.scss file.
app/styles/main.scss
  8:40  error  Files must end with a new line  final-newline

Hey @ericlamarca I'm not too sure about introducing another term for essentially the same thing - we had lots of confusion at the beginning with patterns and components, then we had that naming session. I'd be wary of introducing another term.
I also share your worry about duplication... but that's based on the assumption that users know all the components that are in the manual. My hypothesis is that users might visit the patterns more than the components - because they're full things. Something to test with users?

Hey @bencullimore - yes, exactly. So, do we need to change the h2s 'Elements of the mini-hub' and 'Elements of the A-Z' to say components instead?
Right, I see what you mean, by all means let's test it with users. In the meantime, so all components published in the manual are treated consistently, should we add these new ones to the components list as well?

Merging this to develop to review it on the staging environment.
Discussions above will continue before merging to master.


Update tutorial_users-self-manage-mfa-and-creds.md

Add commas to make policy (json) valid.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I reverted the policy.


Ghost buttons for light theme

Move to ghost buttons to help with light theme display

Merged to main.
Thank you!


Refactored libunshield CMakeLists to build on windows

Create pull request to see if Travis and Appveyor picks it up

Spent some time digging in appveyor docs and i found out how to have separate linux and windows configs in two different yaml files. It is possible to set up the CI for the same repo twice, with different Custom configuration .yml file name file set to .appveyor-windows.yml in first case and .appveyor-linux.yml in second. This is particularly convenient because the build procedure in both cases is diametrally different, splitting into two per-OS configurations makes it more readable and smaller. This is how it looks in practice:
https://ci.appveyor.com/project/kpyrkosz/unshield-windows
https://ci.appveyor.com/project/kpyrkosz/unshield-linux
Notice that the build above (in this PR) still uses the old script.
I've restored your original travis file so it does not contain any of my modifications, the branch is mergable.

Excellent work!!!
Thanks! I'll try to sort this out ASAP but I'm in a busy period right now.

Any progress? :)

Thank you for the kind reminder @kpyrkosz. Maybe just merge? :)
PS. I heard Travis-ci is closing down their .org and we have to migrate to their .com version...

Yes, you can merge, is there any obstacle in the way?

Damn, I shouldn't have squashed it, now I get the git blame....


Synthesis failed for nodejs-document-ai

Hello! Autosynth couldn't regenerate nodejs-document-ai. :broken_heart:
Here's the output from running synth.py:
2020-10-08 03:10:16,319 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-document-ai
2020-10-08 03:10:17,029 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-10-08 03:10:17,032 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-10-08 03:10:17,036 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-10-08 03:10:17,039 autosynth [DEBUG] > Running: git config push.default simple
2020-10-08 03:10:17,042 autosynth [DEBUG] > Running: git branch -f autosynth
2020-10-08 03:10:17,045 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-10-08 03:10:17,051 autosynth [DEBUG] > Running: git clean -fdx
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 706, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 541, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 627, in _inner_main
    metadata = load_metadata(metadata_path)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 55, in load_metadata
    return json.loads(path.read_text())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 45 column 3 (char 1036)

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-document-ai. :sob:
Here's the output from running synth.py:
2020-10-09 02:48:00,503 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-document-ai
2020-10-09 02:48:01,249 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-10-09 02:48:01,253 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-10-09 02:48:01,255 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-10-09 02:48:01,258 autosynth [DEBUG] > Running: git config push.default simple
2020-10-09 02:48:01,261 autosynth [DEBUG] > Running: git branch -f autosynth
2020-10-09 02:48:01,264 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-10-09 02:48:01,295 autosynth [DEBUG] > Running: git clean -fdx
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 706, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 541, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 627, in _inner_main
    metadata = load_metadata(metadata_path)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 55, in load_metadata
    return json.loads(path.read_text())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 45 column 3 (char 1036)

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-document-ai. :sob:
Here's the output from running synth.py:
2020-10-10 03:18:11,729 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-document-ai
2020-10-10 03:18:12,439 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-10-10 03:18:12,443 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-10-10 03:18:12,447 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-10-10 03:18:12,451 autosynth [DEBUG] > Running: git config push.default simple
2020-10-10 03:18:12,455 autosynth [DEBUG] > Running: git branch -f autosynth
2020-10-10 03:18:12,459 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-10-10 03:18:12,489 autosynth [DEBUG] > Running: git clean -fdx
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 706, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 541, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 627, in _inner_main
    metadata = load_metadata(metadata_path)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 55, in load_metadata
    return json.loads(path.read_text())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 45 column 3 (char 1036)

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-document-ai. :sob:
Here's the output from running synth.py:
2020-10-11 02:53:18,003 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-document-ai
2020-10-11 02:53:18,692 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-10-11 02:53:18,694 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-10-11 02:53:18,697 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-10-11 02:53:18,700 autosynth [DEBUG] > Running: git config push.default simple
2020-10-11 02:53:18,703 autosynth [DEBUG] > Running: git branch -f autosynth
2020-10-11 02:53:18,706 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-10-11 02:53:18,736 autosynth [DEBUG] > Running: git clean -fdx
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 706, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 541, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 627, in _inner_main
    metadata = load_metadata(metadata_path)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 55, in load_metadata
    return json.loads(path.read_text())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 45 column 3 (char 1036)

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-document-ai. :sob:
Here's the output from running synth.py:
2020-10-12 02:55:17,565 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-document-ai
2020-10-12 02:55:18,272 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-10-12 02:55:18,276 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-10-12 02:55:18,279 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-10-12 02:55:18,282 autosynth [DEBUG] > Running: git config push.default simple
2020-10-12 02:55:18,285 autosynth [DEBUG] > Running: git branch -f autosynth
2020-10-12 02:55:18,288 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-10-12 02:55:18,318 autosynth [DEBUG] > Running: git clean -fdx
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 706, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 541, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 627, in _inner_main
    metadata = load_metadata(metadata_path)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 55, in load_metadata
    return json.loads(path.read_text())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 45 column 3 (char 1036)

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-document-ai. :sob:
Here's the output from running synth.py:
2020-10-13 03:12:47,813 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-document-ai
2020-10-13 03:12:48,536 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-10-13 03:12:48,539 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-10-13 03:12:48,541 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-10-13 03:12:48,544 autosynth [DEBUG] > Running: git config push.default simple
2020-10-13 03:12:48,547 autosynth [DEBUG] > Running: git branch -f autosynth
2020-10-13 03:12:48,550 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-10-13 03:12:48,579 autosynth [DEBUG] > Running: git clean -fdx
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 706, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 541, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 627, in _inner_main
    metadata = load_metadata(metadata_path)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 55, in load_metadata
    return json.loads(path.read_text())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 45 column 3 (char 1036)

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-document-ai. :sob:
Here's the output from running synth.py:
2020-10-14 02:57:33,525 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-document-ai
2020-10-14 02:57:34,233 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-10-14 02:57:34,237 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-10-14 02:57:34,239 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-10-14 02:57:34,242 autosynth [DEBUG] > Running: git config push.default simple
2020-10-14 02:57:34,245 autosynth [DEBUG] > Running: git branch -f autosynth
2020-10-14 02:57:34,248 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-10-14 02:57:34,277 autosynth [DEBUG] > Running: git clean -fdx
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 706, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 541, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 627, in _inner_main
    metadata = load_metadata(metadata_path)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 55, in load_metadata
    return json.loads(path.read_text())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 45 column 3 (char 1036)

Google internal developers can see the full log here.


Fix #7003. SwiperProps interface doesn't include SwiperOptions fields on TS4

Fix for #7003
Looks like Typescript 4 has some bugs related to imports/exports in .d.ts files. If we make direct imports instead of importing from index.d.ts - everything works. Checked on my project
Any idea why it happens?

Thank you, but Swiper TS definitions are done to support TS v5, this PR can break esnext module resolution. Consider upgrading to TS v5


Feature: markdown table

tf-summarize -md tfplan

returns markdown like this:

CHANGE
NAME

add
module.test-only.github_branch_protection_v3.branch_protection[0]

module.test-only.github_repository.repository

module.test-only.github_team_repository.team_repository_by_slug["xxxxxx"]

module.test-only.github_team_repository.team_repository_by_slug["yyyyyyyyyyy"]

Useful when sending summary as GitHub comment on PR

This is very useful @czerasz-mineiros ... Code changes looks good. I will try to run once in my local and merge it.
Thanks for the contribution @czerasz-mineiros

Released as part of https://github.com/dineshba/tf-summarize/releases/tag/v0.2.2


Steam store button seems to not appear, also lists wrong amount of reviews.

Running latest script on Win11 24H2 (Dev Build 26120.1330), Python version 3.12.3
having "ADD_STEAM_STORE_BUTTON" set to true makes it so that no button is displaying in Discord.

Usually button would be right under the time played, but doesn't exist anymore.
The script also seems to crash when trying to find a price for games only available through a bundle (i.e GTAV)
Setting "ADD_STEAM_STORE_BUTTON" to false seems to bypass this issue as the script maybe doesn't check for prices?
Console output:

Another issue with this seems to be that it is displaying an amount of reviews instead of just the overall rating.

Games steam store page reviews:

Seems to work fine for other games (maybe its the same bundle issue mentioned)

Games steam store page reviews:

unsure what exactly is going on here, i've spent the last couple weeks rewriting/restructuring the entire project on a development branch, so i haven't really been in the loop of how the current stable version of steam presence works
this honestly just seems like steam updating their API behavior or something similar, though the system wasn't really ever super stable in the first place
it should be fixed finish the fabled rewrite (whenever that is done), but for the time being there won't be a fix for this :p

and yeah the finding price of items within a bundle thing is real and it's painful - fabled rewrite should fix it though

can't wait for the rewrite, using the script 24/7 on my PC rn so if u need any testing let me know


⚠ ClamAV has degraded performance

In cbf26b3, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 85 ms

Resolved: ClamAV performance has improved in 4cfcc60.


Question: $facet support in mongo4cats

Hi @Kirill5k ,
Thanks for all the hard work you put into this great project.
I'm looking to build out a pagination feature so that it returns the total number of rows while I page over the results, using the same query (stage) to give me data as well as the full row count. I read about $facet in Mongodb that I'd like to use in mongo4cats, but I don't see any support for facet. Am I overlooking the support or is there a way I can achieve the same functionality using mongo4cats?

Hey @adschwartz,
There is no support for $facet yet, but I can easily add it today.
The only caveat is that I won't be able to release it until next Thursday.

This should now be available in v0.4.9
You can refer to this unit test for a usage example

@Kirill5k This is awesome. I'll start applying this immediately. Looking forward to avoiding my double queries!


nested

Fiddle is worth a thousand words.
Suppose we have an Array property which holds Arrays:
list: {
  type: Array,
  value: [[obj1, obj2,],] // array of arrays of objects
}

and we display these in the DOM with dom-repeats:
<template is="dom-repeat" items="[[list]]" as="innerList">
  <template is="dom-repeat" items="[[innerList]]">
    <paper-checkbox checked="{{item.enabled}}">[[item.name]]</paper-checkbox>
  </template>
</template>

Changing the value of list to a new array of the same values:
this.list = [[obj1, obj2,],];

should (IMO) update all of the data in each dom-repeat. So I should be able to do this:
// Invert the `enabled` value of an object in the nested array.
obj1.enabled = !obj1.enabled;
// Set `list` to a new array so Polymer treats it as a new object and re-binds stuff.
this.list = [[obj1, obj2,],];

But the nested dom-repeat does not update: the checkbox remains the same. I have to do this:
this.set('list.0.0.enabled', !this.list[0][0].enabled);

In my use case, I am replacing the entire array (it may be ordered differently or use different nested arrays entirely) after updating properties of the underlying objects, but the underlying objects in the nested arrays are drawn from a fixed pool rather than created anew each time.
This also repros for arrays of objects with arrays.

All Polymer uses object identity right now. Changing this is not trivial. #3596 for a possible commit path.

This should at least be clearly noted in the docs, especially in cases like templates where you would otherwise expect changes to top-level arrays propagate.
I haven't found a great workaround. Calling notifyPath a hundred times for each sub-property, or cloning all sub-objects whenever the top-level property changes, are both icky.

I faced this issue with 1.9.3 today when trying to reset nested dom-repeat containing array of objects with nested arrrays. Should this be considered as "wontfix" for 1.x?

This has been fixed in Polymer 2: http://jsbin.com/kesurehipi/edit?html,console,output We will not ship a fix for 1.x as it will be a breaking change in terms of data-binding (as objects are now dirty in Polymer 2).


[T2A2][F10-A2]Shi Xiyue

Ready for review

👍 for the attempt! My apologies for the late eval due to your late submission ><".


Change .com Support to Binance.US Support

Accidentally made this PR to the upstream repo, please disregard


DP Singleton in JavaScript

Need to make a readme file which should have the
Definition
Explanation in simple terms
Code related explanation.

Can you assign to me

yeah sure


fix(BREAKING): flip keep_comments to remove_comments

People check for comments in .toString() so we need to keep the comments by default.

Will merge this later when doing more breaking changes in this repo.


feat: current action persistence on abrupt shutdowns

Closes #

Changes

console's HTTP API now has two endpoints:

/logs : accepts a raw-string filter which is used to reload uplink's logger, i.e. tracing_subscriber
/shutdown: Triggers bridge to persist current action with a savefile, before leading to uplink shutting down entirely.

NOTE: action's timeout works like a stopwatch and will only be paused on shutdown, i.e, if action started with timeout of 300s, shutdown was triggered on the clock having 150s left, on uplink restart, there will be 150s till action is deemed to have timedout.
Why?
Allows the user's application to trigger a shutdown in uplink while ensuring persistence of current action information. This is necessary to support OTA updates that might require uplink to be shutdown between action being started and action completion.
Trials Performed

start uplink connected to port 5555 by an application that handles the "lock" action, and takes a long time to complete.

...
    tcp applications:
        name: "1"
        port: 5555
        actions: [ActionRoute { name: "lock", timeout: 300 }]
...
  2023-04-27T15:27:22.645246Z  INFO uplink::base::mqtt: Action = Action { device_id: None, action_id: "345", kind: "process", name: "lock", payload: "{}" }

  2023-04-27T15:27:22.645363Z  INFO uplink::base::bridge: Received action: Action { device_id: None, action_id: "345", kind: "process", name: "lock", payload: "{}" }

  2023-04-27T15:27:22.645414Z  INFO uplink::base::bridge: Action response = ActionResponse { action_id: "345", device_id: None, sequence: 0, timestamp:<PHONE_NUMBER>645, state: "Received", progress: 0, errors: [], done_response: None }
...

From elsewhere, trigger a shutdown a second or two after above logs

#Terminal2:
 curl -X POST http://localhost:3333/shutdown
...
#Terminal1:
  2023-04-27T15:39:34.944052Z  INFO uplink::apis: Shutting down uplink

  2023-04-27T15:39:34.944181Z  INFO uplink::base::bridge: Storing current action in persistence; path: /tmp/uplink/current_action

Restart uplink, without action handler, hence no action completion response, triggering timeout

  2023-04-27T15:51:25.615515Z  INFO uplink::base::bridge: Loading saved action from persistence; action_id: 345
...
  2023-04-27T15:55:46.424650Z ERROR uplink::base::bridge: Timeout waiting for action response. Action ID = 345

This won't save current action on device reboot. We can use this https://rust-cli.github.io/book/in-depth/signals.html

Experimented on this here: https://github.com/bytebeamio/uplink/compare/abrupt-shutdown...signals?expand=1


add the relative entropy

aka kullback leibler divergence

This has mostly been added, but the function could use some cleaning up.
todo:

better docstring
split out cross entropy
allow passing in of joint distributions?
examples, documentation, and tests


Is there a way to replace formGroup with another one

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[x] support request

is there a way to just replace one fromGroup in the FormlyFieldConfig?
When doing reassignement I got error
const config = [].concat(this.fields);
config[0].fieldGroup[0].fieldGroup[index].fieldGroup = fields;
this.fields = config;

not clear to me, could you please provide a stackblitz example, to see what you're trying to achieve.


Default implementation for known embedders

It would be convenient if you can choose some of the well known embedders through a configuration instead of implementing them in embed function manually.
If the desired embedder is not implemented, then you should implement it yourself.

This is tough because all embedders are in python. I don't think this would be possible. The best solution is to run your own infinity embedding service (https://github.com/michaelfeil/infinity) and connect to it using the openai gem.

Actually the proposed feature is to support API based embedding generators like OpenAI and Cohere. Not self-hosted embedding models. What do you think?

That's a good idea. It can use the standard interface of the gem.


Enhancement: Have option to go back a prompt

Right now, there is no obvious option to go back a prompt (inputting an invalid change type does go back a prompt, but it is not in the documentation), which could be useful if you mistype something and go to the next prompt so you don't have to re-make the commit message.

This is a great suggestion. Unfortunately this is out of scope for our project in this course. The best workaround is to regenerate the message after all the prompts have completed.


Expose enable / disable Lua interface

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Expose enable and disable to the Lua interface for better Lua integration
Describe alternatives you've considered
I could use a function to call vim.cmd('SatelliteEnable') (or disable), but those Lua interface would be nice
Additional context
Mind that if it get implemented, both calls could be run before setup. So a call guard might be needed to prevent unexpected behavior.

Asking for things without any justification other than "it would be nice" doesn't really fly
Fair point. My use case was to plug the enable/disable function into my callback directly without a need to use vim.cmd.

Here's the code in my dotfiles that would be benefit by using a lua interface: https://github.com/spywhere/dotfiles/blob/de33a0b0a700b01a57b406db92dc3be57a057a8b/configs/nvim/lua/plugin/appearance/satellite.lua#L40

It looks like what you actually want is:
require('satellite').setup {
  current_only = true,
}

No, that piece of code was to show the scrollbar for a certain amount of time before hiding it, then show it again once I moved the cursor or scroll the window.


报错了～～

Check https://raw.githubusercontent.com/johnspurlock/app-privacy-report-viewer/v0.6/src/app.ts
error: TS18022 [ERROR]: A method cannot be named with a private identifier.
#tryGrowByReslice(n: number) {
  at https://deno.land/std@0.104.0/io/buffer.ts:85:3

TS18022 [ERROR]: A method cannot be named with a private identifier.
#reslice(len: number) {
~~~~~~~~
  at https://deno.land/std@0.104.0/io/buffer.ts:94:3

TS18022 [ERROR]: A method cannot be named with a private identifier.
#grow(n: number) {
~~~~~
  at https://deno.land/std@0.104.0/io/buffer.ts:141:3

Found 3 errors.
----------------------------------

请问这个如何解决。

<EMAIL_ADDRESS>corresponds with deno 1.13.0, so make sure you are running the latest version of deno.
To check which version you are running: $ deno --version
To upgrade: deno upgrade


[FR] Relation/Lookup/Rollup column types

Ability to do relations/lookups in a column. Dataview currently can do this with dot notation ([[link]].field). This is a powerful feature of Notion/Coda databases.
Related is the ability to auto-populate the relation back to the original entity as shown in the Notion screenshot:

The goal of this plugin is to get that Feature! After 1 year of Obsidian I still miss it...

That would be really legendary

Was thinking - would be nice to have a Property type, kind of a Relation property, that lists all the [[backlinks]] linked outwards from the note.

internally can be done with frontmatter fields too. Thanks for your comments @crazymedguy , this feature will arrive sooner or later :)

@RafaelGB hey! Thank you for your product! It's very useful!
Could you tell approximately date of implementing this features?
Dataview relations don't work correctly. And I don't remember solution who can make relation between tables. It's awesome and our team very want to use it!

Hi @DmitryKorzhov , thanks for your support!
Once the base is stable, my intention is to bring this functionality during this year, early next.
This forecast can be reduced depending on the number of collaborations received

I am starting with the most difficult feature until now. Relations

wish me luck, i'll need it =P

An idea how I currently map relations via the DB Folder Plugin: I use the internal linking of Obsidian with two square brackets [[relation]] for the entry in the DB and its relation. Actually the feature of the plugin should only make sure that the relation in the header is recognized as such on the way back. This could also be implemented by copying this relation entry and pasting it below the header. However, one would have to consider how to delete the relation again. Possibly manually. That would not be bad. As long as a relation results in both sides. I try now also at a solution, since I find it important.

The idea is to associate another ddbb to a column. When you select your relation cell, a list of (not filtered) files will be displayed.
https://user-images.githubusercontent.com/11924043/198278223-e3372df4-f06b-4a2c-9671-1786feca7f04.mov
The challenge now its to use the internal values inside the formulas. Natively are not included

Commit 2a706160
2.8.0 is alive with the first version of the relations. Rollup functions will be added during the following versions


Feature Request: Pause/Resume PC

Supersedes:

#110

Background
There are sometimes scenarios where it would be helpful if we can temporarily pause processing without unsubscribing from the topic. In our specific scenario we have a health monitor that needs to be able to pause processing if external resources become unavailable and resume processing once they become healthy again.
Note: One could call pause/resume on the KafkaConsumer but there is no easy way to do this in combination with PC because once PC is running any external operations on the KafkaConsumer becomes unsafe. Calling pause/resume on the KafkaConsumer will race against other calls which the POC does on the KafkaConsumer and calls may fail anytime.
Proposal
I'd be happy to create a PR but I'd like to verify my idea first with you:

Add two methods pausePolling/resumePolling to the AbstractParallelEoSStreamProcessor which delegate to two new methods pausePolling/resumePolling on the BrokerPollSystem.
pausePolling/resumePolling just sets an internal boolean on the BrokerPollSystem. There is no need to physically pause/resume the subscribed partitions on the underlying KafkaConsumer.
The controlLoop evaluates whether or not polling is paused. If paused, it skips polling for new records and instead sleeps (e.g. for 100 ms). However even in paused mode

maybeDoCommit will still be called as there may be work in flight when pause is called which would still be processed.
state changes to draining/closing are still processed to allow clean transitions when the system is shutdown.

I'd explicitly not integrate this with the BrokerPollSystem's internal doPause/resumeIfPaused feature which has a different purpose.

Let me know what you think :).

Released: https://github.com/confluentinc/parallel-consumer/releases/tag/<IP_ADDRESS>


heightForMessageLabel erroneously uses titleLabel text for calculation

I used that approach: http://stackoverflow.com/a/22014311/2150954
and it worked fine. I can make pull request which  solved this issue

It's been awhile, but it's already a pull request (see #103). You're welcome to check it and add feedback, or create your own pull request if you still think it should be solved in a different way.


Extension methods inside factory methods behave inconsistently across analyzer and CFE

Consider main.dart:
main() {
  Foo.withBaz().baz();
}

class Foo {
  Foo();

  factory Foo.withBaz() {
    baz();
    return Foo();
  }
}

extension AddBaz on Foo {
  baz() {
    print('Baz');
  }
}

Analyze and run:
$ dartanalyzer repro.dart
Analyzing repro.dart...
No issues found!
| ~/dev/playground/dart/json/jsonserilizable_ext @ mit-macbookpro3 (mit)
$ dart repro.dart
repro.dart:10:5: Error: Method not found: 'baz'.
    baz();
    ^^^
| ~/dev/playground/dart/json/jsonserilizable_ext @ mit-macbookpro3 (mit)
$

cc @lrhn

The front-end is correct and the analyzer is missing an error.
The baz() invocation in the Foo.withBaz() factory constructor is invalid.
There is no baz declaration in scope, and there is no this in scope, so it's simply an error.
It's the same behavior as if the baz() occurred in a static method.
If the baz() had occurred in a generative constructor or instance method, there would be a this and the baz() would be equivalent to this.baz() which would be a valid implicit extension application.

Analyzer now reports an error:

Instance members can't be accessed from a factory constructor.


neo4j Argocd cluster , shared resources issues fix

Is your feature request related to a problem? Please describe.
well, This is not a feature request but more like a fix to a problem, i just wanted to add it in issues for future refrence if anyone faced this issue
the problem is :
if you are trying to install neo4j cluster with helm + argocd and have auth enabled and loadbalancer enabled. you will face an issue where each argo-cd application for each cluster node will fight to add a label or annotation representing the argocd application name
like this

the helm chart handles helm labels and annotations but doesn't handle argocd annotations which is completely reasonable
work around
using one of argocd feature Diffing Customization
you can add this section to each argocd application and it will stop argocd for trying to solve the label issue
spec:
  ignoreDifferences:
  - group: "*"
    kind: Secret
    name: cluster-auth
    namespace: neo4j
    jsonPointers:
    - /metadata/labels/argocd.argoproj.io~1instance
  - group: "*"
    kind: Service
    name: cluster-lb-neo4j
    namespace: neo4j
    jsonPointers:
    - /metadata/labels/argocd.argoproj.io~1instance

I am not asking for a fix, just wanted to post the workaround somewhere. Thanks


include Transferable interface support for webworkers

need to know what browsers implement the transferable api for webworkers.
see :
https://developer.mozilla.org/en-US/docs/Web/API/Transferable
https://developers.google.com/web/updates/2011/12/Transferable-Objects-Lightning-Fast
https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers#Passing_data_by_transferring_ownership_(transferable_objects)

Duplicate of #1132.


Added utility for taking screenshot of single page element as image

Added utility for taking screenshot of single page element as in-memory image without using of temporary files

@Akkuzin thank you for the pull request!


keep_best_iv should order by iv then cp

Expected Behavior
If we have 3 pokemon of a type and wanted to keep the 2 best IV and two pokemon have the same low IV, we would like to keep the one with max CP
Actual Behavior
[20:25:39] Keep 2 best Slowpoke, based on iv
[20:25:39] Slowpoke [CP 274] [Potential 0.56]
[20:25:39] Slowpoke [CP 172] [Potential 0.51]
[20:25:39] Exchange 1 pokemon(s)
[20:25:39] Exchanging Slowpoke [CP 392] [Potential 0.51] for candy!
Steps to Reproduce
Farm pokemon and have some luck :)
Other Information
OS: OSX
Git Commit: (run 'git log -n 1 --pretty=format:"%H"' and paste it here)
34caa002a464b7665cdcfb531ea3d302632898ac

Fixed by #1472


AttachmentsFormatter function

What do you think of allowing for an attachment formatter function?
The reason is that having meta information formatted as an attachment is not necessarily great for other transports (file, console, etc ...).
By having an attachmentFormatter (or transformer whatever name you prefer) function, it would be possible to convert the generic meta information into attachment just for slack.
    if (this.attachmentFormatter && typeof this.attachmentFormatter === 'function') {
      payload.attachments = this.attachmentFormatter(info)
    } else {
      // for compatibility with the way it currently works
      let attachments = []
      let attachmentKeys = Object.keys(info).filter(key => !isNaN(parseInt(key)))
      attachmentKeys.forEach(key => attachments.push(info[key]))
      payload.attachments = attachments
    }

Well, it took a bit for me to remember to do this, but that's now been implemented! It's a breaking change, but it's for the best in the long term.


Cannot render Matplotlib in VSCode with %matplotlib inline

Applies To

[x] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
I suddenly have trouble rendering plots in Jupyter Notebook ouput in VSCode, even with %matplotlib inline. It only shows e.g. <Figure size 640x480 with 1 Axes>
I came across this issue and updated the ipympl package, but the problem still persists.
Thanks for helping!
VS Code Version
1.75.1
Jupyter Extension Version
v2023.1.2010391206
Jupyter logs
<Figure size 640x480 with 1 Axes>

Coding Language and Runtime Version
Python 3.10.8
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

Thanks for filing this issue and sorry you are running into this issue.
Its possible you have version 8 of the ipywidgets package installed.
This has been fixed in the latest pre-release version

Please install latest VS Code Insiders
Open the extensions page, search for Jupyter and click the button Switch to Pre-Release Version
Similarly please install the latest Pre-Release version of the Python extension

If that does not work, please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to verbose
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel.

Thank you very much, that did it for me!


[Suggestion] Energy ratios

Is there any way Mekanism could support values lower than 0.1? For example 0.08 or 0.001 to make it possible to bring it in line with other tech mods easily like IC2. For example as it is right now with 0.1 the standard solar panel in Mekanism is over twice as fast as the IC2 one.

Mekanism can support energy values much smaller than 0.1. Everything can be modified in the config.


Update list command in user guide

Codecov Report

Merging #34 (7c66999) into master (1c85ebb) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #34   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1c85ebb...7c66999. Read the comment docs.


PlutusV3 Feature Support

Added

Cryptographic hashing utilities:- pripemd_160, pkeccak_256, and pblake2b_224 to Plutarch.Crypto
PlutusV3 BLS primitives to Plutarch.BLS
PlutusV3 Bitwise primitives to Plutarch.Bitwise

Changed

Bumped plutus-core version to <IP_ADDRESS>
Updated getArity mapping to handle the new builtins in Plutarch.Internal
Updated printScript in Plutarch.Internal.Other to new PlutusCore version.

@peter-mlabs
@SeungheonOh
Review please.

Primops added are

CIP-122 Bitwise primops on ByteString
CIP-123 Logical primops on ByteString
CIP-381 BLS12-381 primops
CIP-101 keccak256 primop
CIP-127 ripemd_160 primop

Implementations looks good to me, it can use little documentations, but that can be added later

Thank you. Looks good to me. Ideally we push some tests as well. I'll see if I can pull some time somewhere to work on it hopefully.

module Testing.Crypto where
import Test.Tasty
import Test.Tasty.HUnit
import Test.Tasty.QuickCheck as QC
import Testing.Eval (psucceeds, passert, toHexString)
import Plutarch.Prelude
import PlutusCore.Crypto.Hash qualified as Hash
tests :: TestTree
tests = testGroup "PlutarchV3 Builtins"
  [ testCase "keccak_256" $
      passert $
        (pkeccak_256 # (phexByteStr "4dd6d57ca8cb7ac8c3b219366754a392ba9e4e43b6b3ae59d89be3f878ba8fb6"))
            #== phexByteStr "1994466d51e80d6dc32c8f41f142b47b2d03b4f5fa869aced6157c016b2b331d"
  , testCase "pblake2b_224" $
      passert $
        (pblake2b_224 # (phexByteStr "4dd6d57ca8cb7ac8c3b219366754a392ba9e4e43b6b3ae59d89be3f878ba8fb6"))
            #== pconstant (Hash.blake2b_224 $ toHexString "4dd6d57ca8cb7ac8c3b219366754a392ba9e4e43b6b3ae59d89be3f878ba8fb6")
  , testCase "pripemd_160" $
      passert $
        (pripemd_160 # (phexByteStr "4dd6d57ca8cb7ac8c3b219366754a392ba9e4e43b6b3ae59d89be3f878ba8fb6"))
            #== pconstant (Hash.ripemd_160 $ toHexString "4dd6d57ca8cb7ac8c3b219366754a392ba9e4e43b6b3ae59d89be3f878ba8fb6")
  ]


CloudFormation Visual Studio Code extension

Thanks @PatMyron
Going to close this MR as I added it manually for now.
Also added you as a contributor on the README.
Thanks for the contribution 🚀


Experiment with new balance animation

Let's plan to switch on this one and remove the legacy one, once Surf migrates on it.
Plus we'll be able to close the following PR

Yep, we'll do, just have some design discussions and decisions going, stay in touch ;)


Update azure storage blob dependency to 12.22.2  from 12.21.1

Description
Updates Azure storage blob dependency to 12.22.2 after #7914 failed.
Related Issues
Resolves #[Issue number to be closed when this PR is merged]

#7914
Check List

[ ] ~New functionality includes testing.~

[ ] ~All tests pass~

[ ] ~New functionality has been documented.~

[ ] ~New functionality has javadoc added~

[x] Commits are signed per the DCO using --signoff
[ ] ~Commit changes are listed out in CHANGELOG.md file (See: Changelog)~

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@scrawfor99 thank you for doing this, we used to have changelog for dependencies (but I cannot use dependabot for that anymore), could you ad one please?

Hi @reta, sorry I did not realize that. Should be all set.


Release version 1.0

Once we deliver #5 we can release the version 1.0 as a zip file

Done: https://github.com/IBM/javacore-analyser/releases/download/v1.0/javacore-analyser_v_1_0.zip


Example

Hi @markjaquith
You don't happen to have an example how to use this in PlayWright? 😀
I'm pretty new to SvelteKit and Playwright so anything pointing me in the right direction would be great 👍😀

@seesharper
So in your Playwright test, you'd import like:
import { mockFetch } from 'sveltekit-playwright-fetch-mock'

And then:
test('Example.com test', async ({ page }) => {
	await mockFetch(page, /^https:\/\/www\.example\.com\//, {
		somedata: 'example',
	})
	await page.goto('/some-local-route-that-fetches-example-dot-com')
	// Your assertions here.
})

So what this means is that when you go to /some-local-route-that-fetches-example-dot-com in your SvelteKit app, and the +page.server.js or +page.server.ts file for that route calls fetch (using the one that SvelteKit provides you) to get data from https://www.example.com/, this package will intercept that request and return { somedata: "example" }

Thanks a lot for responding so fast 😍.
This is what I've got so far
test('Example.com test', async ({ page }) => {
	await mockFetch(page, /^https:\/\/www\.nrk\.no\//, {
		somedata: 'example',
	});
	await page.goto('/login')
	// Your assertions here.
})

+page.server.ts
import type { ServerLoadEvent } from '@sveltejs/kit';
import type { PageServerLoad } from './$types';

export const load = (async (event: ServerLoadEvent) => {

    let response = await event.fetch("https://www.nrk.no/")
    console.log(response);

    return { res: response.text() };
}) satisfies PageServerLoad;

+page.svelte
<script lang="ts">
	import type { PageServerData } from './$types';

	export let data: PageServerData;
</script>

<h1>{data.res}</h1>

I still can't get it to return the mocked result. Do you see any obvious mistake here? 😃

The only mistakes are mine. One was fixed in version 0.5.3 — I created this package for use in a specific project, and I had accidentally left in a tiny bit of config that was unique to that project.
Next, there are more setup steps than I've outlined.
Here are the full instructions. I know it's a lot... not sure if there's a way to make it simpler.
src/hooks.server.ts
import type { HandleFetch, Handle } from '@sveltejs/kit'
import { sequence } from '@sveltejs/kit/hooks'
import {
	handle as handleHttpMocks,
	handleFetch as handleMockedResponses,
} from 'sveltekit-playwright-fetch-mock'
import { PUBLIC_LOCAL } from '$env/static/public'

export const handle = sequence(
	handleHttpMocks(PUBLIC_LOCAL === '1'),
) satisfies Handle

export const handleFetch = (async ({ request, fetch, event }) => {
	const mockedResponse = handleMockedResponses(request, event)

	if (mockedResponse) {
		return mockedResponse
	}

	return fetch(request)
}) satisfies HandleFetch

In your local and CI environments, add PUBLIC_LOCAL=1 to your environment.
This is what tells the mock code to be active. You can name this however you like, if you also change the reference in src/hooks.server.ts to match it.
src/app.d.ts
type FetchMocks = Record<
	string,
	{
		status: number
		statusText: string
		headers?: Record<string, string>
		body: string
	}
>

declare namespace App {
	// interface Error {}
	interface Locals {
		fetchMocks: FetchMocks
		isPlaywright: boolean
	}
	// interface PageData {}
	// interface Platform {}
}

And finally in your Playwright test:
import { expect, test } from '@playwright/test'
import { mockFetch } from 'sveltekit-playwright-fetch-mock'

test('Example.com test', async ({ page }) => {
	await mockFetch(page, /^https:\/\/www\.example\.com\//, {
		somedata: 'example',
	})
	await page.goto('/some-local-route-that-fetches-example-dot-com')
	// Your Playwright assertions here.
})

So what this means is that when you go to /some-local-route-that-fetches-example-dot-com in your SvelteKit app, and the +page.server.js or +page.server.ts file for that route calls fetch (using the one that SvelteKit provides you) to get data from https://www.example.com/, this package will intercept that request and return { somedata: "example" }

Here is a full working example: https://github.com/markjaquith/sveltekit-playwright-fetch-mock-example

Ah, I just started looking into SvelteKit hooks before I left the office today. Had a feeling we were missing something to glue the whole thing together 😃. Again thanks a lot for taking the time to explain this in such detail. Appreciate it 👍😍

It worked perfectly 👍. Thanks 😃


Get  list of conflicted files.

alias added for the list of conflicted files.

Just use one of the aliases to git status.


Custom axis place using category names.

Added a new method for category charts to create custom axis places by
using category names in first series.
#217

Excellent! Did you try it out in a demo chart yet?

Yes, see TestForTickCalculatorCustom.java :

Thanks. Really great!


MNT: Add noarch: python

Hi! This is the friendly automated conda-forge-webservice.
I've made the recipe noarch: python as instructed in #42.
Here's a checklist to do before merging.

[ ] Bump the build number if needed

Fixes #42

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

❌ noarch packages can't have skips with selectors. If the selectors are necessary, please remove noarch: python.
❌ noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

ℹ The recipe is not parsable by parser conda-souschef (grayskull). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11993325613. Examine the logs at this URL for more detail.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Closing as this package is not a pure python package: https://github.com/facebookresearch/fairseq/tree/main/fairseq/clib
Sorry for the noise!