BIGTOP-3967: add support for spark

Description of PR
Add support for spark component, include compile command and problem.

install R by dnf in openEuler
add pandoc by wget and install in openEuler

How was this patch tested?
build command
docker run --rm -v pwd:/home/bigtop --workdir /home/bigtop bigtop/slaves:trunk-openeuler-22.03-aarch64 bash -c '. /etc/profile.d/bigtop.sh; ./gradlew spark-pkg'
smoke test command
./docker-hadoop.sh -C config_openeuler-22.03.yaml -c 3 -s
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (BIGTOP-3967)
[ ] Make sure that newly added files do not have any licensing issues. When in doubt refer to https://www.apache.org/licenses/

Update the spec file(commit: https://github.com/apache/bigtop/pull/1148/commits/a0a68f101bd48edfe1ef0376c43c034f328107a4), becasue we met the error in rockyLinux:

We found the %elif need the version of RPM is 4.15.0+, but rockyLinux's version is 4.14.3

Spark smoke test successful log on openEuler

The detail log:
https://gitee.com/macchen1/bigtop/blob/master/smoke-test-log/openeuler-smoke-log/spark-openeuler.log

Spark smoke test successful log on RocklyLinux

The detail log：
https://gitee.com/macchen1/bigtop/blob/master/smoke-test-log/rocklylinux-8-smoke-log/spark-rocklylinux-8.log
@guyuqi

@guyuqi

@guyuqi
When I test the bigtop smoke test of the Ubuntu 22.04 system, the apt repository cannot be found.

I build the local repository source command:  ./gradlew apt
Can you provide a way to test the smoke test of bigtop on Ubuntu 22.04?

@guyuqi When I test the bigtop smoke test of the Ubuntu 22.04 system, the apt repository cannot be found.  I build the local repository source command: ./gradlew apt Can you provide a way to test the smoke test of bigtop on Ubuntu 22.04?

In Ubuntu-22.04 yaml:
https://github.com/apache/bigtop/blob/master/provisioner/docker/config_ubuntu-22.04.yaml
You should enable your local repo and set the components properly like:
components: [hdfs, yarn, mapreduce, hbase]
enable_local_repo: true
smoke_test_components: [hbase]

To run the smoke test:
./docker-hadoop.sh -C config_ubuntu-22.04.yaml -c 3 -s

@guyuqi
My operation is the same as you said, but it's wrong.

@guyuqi When I test the bigtop smoke test of the Ubuntu 22.04 system, the apt repository cannot be found.  I build the local repository source command: ./gradlew apt Can you provide a way to test the smoke test of bigtop on Ubuntu 22.04?

In Ubuntu-22.04 yaml: https://github.com/apache/bigtop/blob/master/provisioner/docker/config_ubuntu-22.04.yaml You should enable your local repo and set the components properly like:
components: [hdfs, yarn, mapreduce, hbase]
enable_local_repo: true
smoke_test_components: [hbase]

To run the smoke test: ./docker-hadoop.sh -C config_ubuntu-22.04.yaml -c 3 -s

@guyuqi
My operation is the same as you said, but it's wrong.

I just successfully verified zookeeper on my local ubuntu-22 environment:
components: [zookeeper]
enable_local_repo: true
smoke_test_components: [zookeeper]

The yaml should be:
docker:
        memory_limit: "4g"
        image:  "bigtop/puppet:trunk-ubuntu-22.04"
        repo: "http://repos.bigtop.apache.org/releases/3.2.0/ubuntu/22.04/$(ARCH)"
distro: debian
components: [zookeeper]
enable_local_repo: true
smoke_test_components: [zookeeper]

You should not modify the field: repo.
The field enable_local_repo: true has enabled your local repo.
If we enable local repo, we should also build the prerequisite components : bigtop-utils, bigtop-jsvc and bigtop-groovy and don't forget to setup apt repo at last.
./gradlew bigtop-utils-pkg bigtop-groovy-pkg bigtop-jsvc-pkg zookeeper-pkg apt

./gradlew bigtop-utils-pkg bigtop-groovy-pkg bigtop-jsvc-pkg

I have built all prerequisite components and apt, but the error still occurs.

the error:

The related field repo should not be changed to your local repo file:///bigtop-home/output

./gradlew bigtop-utils-pkg bigtop-groovy-pkg bigtop-jsvc-pkg

I have built all prerequisite components and apt, but the error still occurs.  the error:

May I ask how did you build these components?

Please build the components based in docker images bigtop/slaves:3.2.0-ubuntu-22.04-aarch64.
Please build the components under the user: jenkins.

We moved R and Pandoc into bigtop_toolchain, compile and smoke test successfully.
The openEuler successful log:

The detail log:
https://gitee.com/macchen1/bigtop/blob/master/smoke-test-log/openeuler-smoke-log/spark-openeuler-change-to-bigtop_toolchain.log
The rocklylinux successful log:

The detail log:
https://gitee.com/macchen1/bigtop/blob/master/smoke-test-log/rocklylinux-8-smoke-log/spark-change-bigop_tooltain-rockly-8.log
@guyuqi

@guyuqi Thanks for your help and advice.

Moved R and pandoc installation into bigtop_toolchain, smoke test successfully: https://github.com/apache/bigtop/pull/1148#issuecomment-1665288175
Add comments for openEuler currently does not support PowerPC. (commit:https://github.com/apache/bigtop/commit/d2e8e4ecfc96b2208cc97381c2978c56a53ded72)
The discussion about compile/smokeTest is ok on ubuntu-22.04, ambari/kafka/solr/zk smoke test successfully, you can get the detail log: https://gitee.com/macchen1/bigtop/tree/master/smoke-test-log/ubuntu-22-smoke-log
and we will push the other smoke test log on it.

@guyuqi Thanks for your help and advice.

Moved R and pandoc installation into bigtop_toolchain, smoke test successfully: BIGTOP-3967: add support for spark #1148 (comment)
Add comments for openEuler currently does not support PowerPC. (commit:d2e8e4e)
The discussion about compile/smokeTest is ok on ubuntu-22.04, ambari/kafka/solr/zk smoke test successfully, you can get the detail log: https://gitee.com/macchen1/bigtop/tree/master/smoke-test-log/ubuntu-22-smoke-log
and we will push the other smoke test log on it.

I rebuilt openEuler docker image and tried to build Hadoop and Spark with this image.
It failed to build Hadoop:
[INFO] [2/4] Fetching packages...
[INFO] error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">= 14.0.0". Got "12.22.1"
[INFO] error Found incompatible module.
[INFO] error Found incompatible module.info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Hadoop Main 3.3.5:
...
.
.
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  27:38 min
[INFO] Finished at: 2023-08-15T06:00:24Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.11.2:yarn (yarn install) on project hadoop-yarn-applications-catalog-webapp: Failed to run task: 'yarn ' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :hadoop-yarn-applications-catalog-webapp

@MacChen01

@guyuqi Thanks for your help and advice.

Moved R and pandoc installation into bigtop_toolchain, smoke test successfully: BIGTOP-3967: add support for spark #1148 (comment)
Add comments for openEuler currently does not support PowerPC. (commit:d2e8e4e)
The discussion about compile/smokeTest is ok on ubuntu-22.04, ambari/kafka/solr/zk smoke test successfully, you can get the detail log: https://gitee.com/macchen1/bigtop/tree/master/smoke-test-log/ubuntu-22-smoke-log
and we will push the other smoke test log on it.

I rebuilt openEuler docker image and tried to build Hadoop and Spark with this image. It failed to build Hadoop:
[INFO] [2/4] Fetching packages...
[INFO] error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">= 14.0.0". Got "12.22.1"
[INFO] error Found incompatible module.
[INFO] error Found incompatible module.info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Hadoop Main 3.3.5:
...
.
.
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  27:38 min
[INFO] Finished at: 2023-08-15T06:00:24Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.11.2:yarn (yarn install) on project hadoop-yarn-applications-catalog-webapp: Failed to run task: 'yarn ' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :hadoop-yarn-applications-catalog-webapp

@MacChen01

This bug?
https://issues.apache.org/jira/browse/BIGTOP-3960
@guyuqi

@guyuqi Thanks for your help and advice.

Moved R and pandoc installation into bigtop_toolchain, smoke test successfully: BIGTOP-3967: add support for spark #1148 (comment)
Add comments for openEuler currently does not support PowerPC. (commit:d2e8e4e)
The discussion about compile/smokeTest is ok on ubuntu-22.04, ambari/kafka/solr/zk smoke test successfully, you can get the detail log: https://gitee.com/macchen1/bigtop/tree/master/smoke-test-log/ubuntu-22-smoke-log
and we will push the other smoke test log on it.

I rebuilt openEuler docker image and tried to build Hadoop and Spark with this image. It failed to build Hadoop:
[INFO] [2/4] Fetching packages...
[INFO] error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">= 14.0.0". Got "12.22.1"
[INFO] error Found incompatible module.
[INFO] error Found incompatible module.info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Hadoop Main 3.3.5:
...
.
.
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  27:38 min
[INFO] Finished at: 2023-08-15T06:00:24Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.11.2:yarn (yarn install) on project hadoop-yarn-applications-catalog-webapp: Failed to run task: 'yarn ' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :hadoop-yarn-applications-catalog-webapp

@MacChen01

This bug? https://issues.apache.org/jira/browse/BIGTOP-3960 @guyuqi

oops, I forgot that I have fixed this issue in https://github.com/apache/bigtop/pull/1133.
Let me cherry pick it to openEuler Branch.

Spark smoke test successfully using bigtop/puppet, the log is:
The detail log is: https://gitee.com/macchen1/bigtop/blob/master/smoke-test-log/openeuler-puppet-smoke-log/spark-openeuler.log
@guyuqi pls help to check the code we push, thanks.

Let me re-build the bigtop_toolchain images and verify the PR #1148 #1147 #1143 together.
Thanks.
@MacChen01

Spark smoke test successfully using bigtop/puppet, the log is:
The detail log is: https://gitee.com/macchen1/bigtop/blob/master/smoke-test-log/openeuler-puppet-smoke-log/spark-openeuler.log
@guyuqi pls help to check the code we push, thanks.

Let me re-build the bigtop_toolchain images and verify the PR #1148 #1147 #1143 together. Thanks. @MacChen01

ok, thanks.

It failed to build Spark based on openEuler toolchain images:
...

Error in loadVignetteBuilder(pkgdir, TRUE) :
  vignette builder 'knitr' not found
Execution halted
error: Bad exit status from /var/tmp/rpm-tmp.6j91xO (%build)
...

Kengo had fixed the similar issue in https://issues.apache.org/jira/browse/BIGTOP-3540.
It appears R was not installed in openEuler properly.
Please refer to PR #776 .
Thanks. @MacChen01

I applied the patches from PRs:  #1148, #1147 and #1143 yesterday.
Built toolchain images: bigtop/puppet:est-openeuler-22.03-aarch64 and bigtop/slaves:test-openeuler-22.03-aarch64.
Built Spark in bigtop/slaves:test-openeuler-22.03-aarch64.
@uscxiexing

I also cherry-pick some patches from master to branch openEuler-support several days ago.
Please keep your local branch updated. Thanks.

I'd like to build toochain and Spark again in a new node and make double check.
I will update the status here later.
Thanks.
@uscxiexing

I'd like to build toochain and Spark again in a new node and make double check. I will update the status here later. Thanks. @uscxiexing

Thank you, I'm also re-running this pr and build spark.

It failed to build Spark based on openEuler toolchain images:
...

Error in loadVignetteBuilder(pkgdir, TRUE) :
  vignette builder 'knitr' not found
Execution halted
error: Bad exit status from /var/tmp/rpm-tmp.6j91xO (%build)
...

Kengo had fixed the similar issue in https://issues.apache.org/jira/browse/BIGTOP-3540. It appears R was not installed in openEuler properly. Please refer to PR #776 .
Thanks. @MacChen01

We didn't modify the code about this, as you see the bugfix has merged into master branch, please help to check it.
And we will check and verfiy again.
@guyuqi

@guyuqi
we checked and verfiy again.Build  spark successful ，and smoke test is also successful.
compile spark successful log:
the time zone is UTC .

smoke test  successful log:

we check and verfiy successfully.
@guyuqi

we check and verfiy successfully. @guyuqi

Sorry, I have been caught up with other things. I will test it ASAP.

PR #1143 #1147 and #1148 have been merged.
Thanks, @MacChen01 @uscxiexing

PR #1143 #1147 and #1148 have been merged. Thanks, @MacChen01 @uscxiexing

Thanks @guyuqi


 I ask because CreateCompletion() defaults to "/completions"  not the  "/moderations" urlSuffix on the completion request? Please advise.

@sashabaranov never mind, this is already implemented in moderation.go. I think this issue should be closed then.


Original javascript variable is not updated via components

Description of the bug:
Procedure is included: https://jsfiddle.net/js3ak747/7/

aa is a primitive value (a string), so it gets copied when you assign it to myData and myData2. That's just how javascript works. Ractive allows you to pass primitives into components and keeps them in sync, but it is fully in control of the data mapped between parent and child component.
If aa were a reference and you modified one of it's properties, that would work (see https://jsfiddle.net/martypdx/9Lx1z39m/).
Though if you assign the same object to two references (myData and myData2), Ractive still won't know that those ref to the same thing (unless you explicit tell it via ractive.update). Is there a reason you could use the same data twice like in your example?

OK, I remembered the same string issue in Python as you told. I'm still happy to use object or list, as in this fiddle: https://jsfiddle.net/9Lx1z39m/1/
We are creating a component library with Ractive (like jquery-ui's) and I want to be sure that the component will update its view as its javascript data is changed by anyone.
Possible scenario: Think of two distinct components. One is a datatable, listing contents and allows editing a list of objects, other is a pie-chart that visualizes and permits editing a datatable in another format.
my data contains: hobby-name, where-i-learnt, how-much-do-i-like
I should pass whole data to my  <datatable ...>
I should pass only hobby-name and how-much-do-i-like columnsto<pie-chart ...>.  So andshould use two distinctractive.data` as they accept different number of columns.
A really pseudo code-ish  example for this purpose is as follows: https://jsfiddle.net/9Lx1z39m/2/

Way late, but ractive doesn't track separate references to the same data unless you link it. Links are available starting in 0.8.
With your fiddle, ractive doesn't know the myData[1] and myCheckbox are the same object. It sounds like having an observer keep the two sides in sync would be your best bet, since the data doesn't exactly line up on either side.
https://jsfiddle.net/9Lx1z39m/4/


Deploy Checklist: New Expensify 2021-12-06

Release Version: 1.1.18-3
Compare Changes: https://github.com/Expensify/App/compare/production...staging
This release contains changes from the following pull requests:

https://github.com/Expensify/App/pull/5275

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/5805

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/5921

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6207

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6230

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6259

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6272

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6294

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6367

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6384

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6413

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6455

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6461

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6469

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6476

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6477

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6499

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6500

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6501

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6515

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6523

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6524

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6531

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6535

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6536

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6538

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6542

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6543

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6544

[x] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6545

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6548

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6550

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6555

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6557

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6559

[x] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6561

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6576

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6578

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/6582

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6586

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6597

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6600

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/6601

[ ] QA
[ ] Accessibility

Internal QA:

[ ] https://github.com/Expensify/App/pull/6411 - @sketchydroide @marcaaron

Deploy Blockers:

[ ] https://github.com/Expensify/App/issues/6528
[x] https://github.com/Expensify/App/issues/6609
[x] https://github.com/Expensify/App/issues/6610
[x] https://github.com/Expensify/App/issues/6612
[x] https://github.com/Expensify/App/issues/6614
[x] https://github.com/Expensify/App/issues/6618
[x] https://github.com/Expensify/App/issues/6620
[x] https://github.com/Expensify/App/issues/6627

cc @Expensify/applauseleads

📣 @applausebot You have been assigned to this job by @OSBotify!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

Checked off a number of PRs which were already CP'd to staging and then deployed to production, and thus should not be included in this checklist. Also checked off #6536, which is listed as No QA.

Starting QA

Posting this here as well - https://expensify.slack.com/archives/C9YU7BX5M/p1638900800215400
We're currently unable to access build 1.1.18-1 on Android. Build available in Playstore is 1.1.17-7 (seems there was an issue surrounding the last deploy for 1.1.18-1)

Regression is still in progress. Updates so far
Deploy Blockers

https://github.com/Expensify/App/issues/6609
https://github.com/Expensify/App/issues/6620
https://github.com/Expensify/App/issues/6627

Issues found

https://github.com/Expensify/App/issues/6613
https://github.com/Expensify/App/issues/6621
https://github.com/Expensify/App/issues/6622
https://github.com/Expensify/App/issues/6623
https://github.com/Expensify/App/issues/6625
https://github.com/Expensify/App/issues/6628

Regression TCs

Create group and User search steps are blocked by #6609
Bank Account TCs are blocked by #6620
Android TCs are blocked by the missing build https://github.com/Expensify/App/issues/6605#issuecomment-988163227

Checking off https://github.com/Expensify/App/pull/6544 > https://github.com/Expensify/App/issues/6627#issuecomment-988302460

I think #6620 can be checked off now. Issue is resolved for me on staging when re-testing.

Looks like the fix to https://github.com/Expensify/App/issues/6528 is being CP'd to staging in 1.1.18-3 here

So to recap where we'll ideally be after 1.1.18-3 is finished deploying:

We should be able to retest any deploy blockers and they should all be resolved.
These regression TC's should be unblocked:

Create group and User search steps
Bank Account TCs

I see nothing in the Google Play Console that might indicate why the Android builds wouldn't be available. Reached out for clarification in slack. Hopefully we'll be able to get this sorted.

Checking #5805 > https://github.com/Expensify/App/issues/6610#issuecomment-987682397
Checking #6597 >https://github.com/Expensify/App/issues/6623#issuecomment-988103027

#6620 is resolved, we are re-testing blocked steps

Regression is Completed
TR steps re-tested
Blocked PRs re-tested too
Checking off #6542, #6524, 6230, #6477
New issue https://github.com/Expensify/App/issues/6640 From PR #6582. We didn't mark it as Deploy Blocker as its repro in PROD. Is it PROD PR? @roryabraham @chiragsalian  let us know
https://github.com/Expensify/App/pull/6557#issuecomment-987427913 - Can we check it off ?

https://github.com/Expensify/App/pull/6557#issuecomment-987427913 has been reverted, so we can check it off

@roryabraham
Only https://github.com/Expensify/App/pull/6582 is pending now with issue #6640.
Should we consider it a blocker or we can check off and close this checklist?

I think https://github.com/Expensify/App/pull/6582 and https://github.com/Expensify/App/issues/6640 should not be treated as blockers since email responses aren't formatted correctly on production anyways. So we can probably check off https://github.com/Expensify/App/pull/6582 on this checklist despite the fact it didn't really pass QA cc @chiragsalian
So I think the only other question is #6528

@roryabraham its a pass on Android

It seems like this Checklist is ready to deploy.

:shipit:


Too many concurrent aggregations when conducting image geemap.image_stats_by_zone

Environment Information
Please run the following code on your computer and share the output with us so that we can better debug your issue:
import geemap
geemap.Report()

Fri Oct 21 18:07:14 2022 Eastern Daylight Time
OS | Windows | CPU(s) | 12 | Machine | AMD64
Architecture | 64bit | RAM | 15.8 GiB | Environment | Jupyter
Python 3.10.6 | packaged by conda-forge | (main, Oct 7 2022, 20:14:50) [MSC v.1916 64 bit (AMD64)]
geemap | 0.17.1 | ee | 0.1.326 | ipyleaflet | 0.17.0
folium | 0.12.1.post1 | jupyterlab | 3.4.8 | notebook | 6.4.12
ipyevents | 2.0.1 | geopandas | 0.11.1 | localtileserver | 0.6.0
Description
Hi Prof.Wu and other gee users,
I tried to calculate the fraction of species habitat in each gridded cropland cell globally at 10 km resolution using the tool of geemap.image_stats_by_zone. I created an image of the overlapping areas between species habitat and croplands at 100 m resolution. There are about 0.4 million grid cells of croplands, which means 0.4 million zones existed when running the tool. However, it encountered an issue of  "too many concurrent aggregations".  I tried to add the argument of tileScale in the image_stats_by_zone, but this tool did not include the tileScale argument. An option is to clip the image of croplands into a bunch of smaller images. But this is not reasonable to conduct global analysis. How can I address this issue? Do you have any tips? Thank you very much for your help. I would really appreciate it.
What I Did
The code is as follows:

fraction="fraction_value.csv"
proportion=geemap.image_stats_by_zone(species_cropland_overlapping, croplands, fraction, scale=100, reducer="PERCENTAGE")
The information of the image of croplands:
{'type': 'Image',
 'bands': [{'id': 'b1',
   'data_type': {'type': 'PixelType',
    'precision': 'int',
    'min': -2147483648,
    'max':<PHONE_NUMBER>},
   'dimensions': [4228, 1453],
   'crs': 'EPSG:4326',
   'crs_transform': [0.0833333,
    0,
    -173.99998128000004,
    0,
    -0.0833333,
    66.49989425999999]}],
 'version':<PHONE_NUMBER>268685,
 'id': 'users/deqiangm/Cropland',
 'properties': {'system:footprint': {'type': 'LinearRing',
   'coordinates': [[-121.67122610462616, 66.54172697234613],
    [-174.16747359083948, 66.5397527478766],
    [-174.10214171930795, -54.62350296623143],
    [-138.18293833538195, -54.62521907542034],
    [-85.89584980341812, -54.62521904903288],
    [-41.86461744690978, -54.62521909521001],
    [7.670518944336254, -54.62521906304687],
    [51.70175136275029, -54.62521910061934],
    [87.47712772032244, -54.62521907955642],
    [142.5161681858667, -54.62521909292239],
    [178.43537157414028, -54.623502975270476],
    [178.50070336935985, 66.53975271087087],
    [95.7329837040513, 66.54172693631179],
    [54.45370323628766, 66.54172694955639],
    [-0.5853370500396582, 66.54172693801144],
    [-80.39194577432268, 66.54172695157293],
    [-121.67122610462616, 66.54172697234613]]},
  'system:asset_size': 1617594}}

The information of the image of the overlap between species habitats and croplands:
{'type': 'Image',
'bands': [{'id': 'area',
'data_type': {'type': 'PixelType', 'precision': 'double'},
'crs': 'EPSG:4326',
'crs_transform': [1, 0, 0, 0, 1, 0]}]}
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.
```
---------------------------------------------------------------------------
HttpError                                 Traceback (most recent call last)
File ~\Anaconda3\envs\gee\lib\site-packages\ee\data.py:328, in _execute_cloud_call(call, num_retries)
    327 try:
--> 328   return call.execute(num_retries=num_retries)
    329 except googleapiclient.errors.HttpError as e:

File ~\Anaconda3\envs\gee\lib\site-packages\googleapiclient\_helpers.py:134, in positional.<locals>.positional_decorator.<locals>.positional_wrapper(*args, **kwargs)
    133         logger.warning(message)
--> 134 return wrapped(*args, **kwargs)

File ~\Anaconda3\envs\gee\lib\site-packages\googleapiclient\http.py:915, in HttpRequest.execute(self, http, num_retries)
    914 if resp.status >= 300:
--> 915     raise HttpError(resp, content, uri=self.uri)
    916 return self.postproc(resp, content)

HttpError: <HttpError 429 when requesting https://earthengine.googleapis.com/v1alpha/projects/earthengine-legacy/value:compute?prettyPrint=false&alt=json returned "Too many concurrent aggregations.". Details: "Too many concurrent aggregations.">

During handling of the above exception, another exception occurred:

EEException                               Traceback (most recent call last)
Cell In [9], line 3
      1 #calculate total proportion of overlapping areas in each grid
      2 fraction="fraction_species.csv"
----> 3 proportion=geemap.image_stats_by_zone(total_area,Land_type,fraction,scale=100,reducer="SUM")
      4 landcover.getInfo()

File ~\Anaconda3\envs\gee\lib\site-packages\geemap\common.py:7444, in image_stats_by_zone(image, zones, out_csv, labels, region, scale, reducer, bestEffort, **kwargs)
   7441     return ee.Image().set({"zone": value}).set({"stat": stat.values().get(0)})
   7443 collection = ee.ImageCollection(values.map(lambda x: get_stats(x)))
-> 7444 keys = collection.aggregate_array("zone").getInfo()
   7445 values = collection.aggregate_array("stat").getInfo()
   7447 if labels is not None and isinstance(labels, list):

File ~\Anaconda3\envs\gee\lib\site-packages\ee\computedobject.py:98, in ComputedObject.getInfo(self)
     92 def getInfo(self):
     93   """Fetch and return information about this object.
     94
     95   Returns:
     96     The object can evaluate to anything.
     97   """
---> 98   return data.computeValue(self)

File ~\Anaconda3\envs\gee\lib\site-packages\ee\data.py:757, in computeValue(obj)
    754 if workload_tag:
    755   body['workloadTag'] = workload_tag
--> 757 return _execute_cloud_call(
    758     _get_cloud_api_resource().projects().value().compute(
    759         body=body,
    760         project=_get_projects_path(),
    761         prettyPrint=False))['result']

File ~\Anaconda3\envs\gee\lib\site-packages\ee\data.py:330, in _execute_cloud_call(call, num_retries)
    328   return call.execute(num_retries=num_retries)
    329 except googleapiclient.errors.HttpError as e:
--> 330   raise _translate_cloud_exception(e)

EEException: Too many concurrent aggregations.

See this example: https://book.geemap.org/chapters/06_data_analysis.html#zonal-statistics-with-two-images
The second parameter should be a zone image with discrete values. I don't think your croplands image is the right input.

See this example: https://book.geemap.org/chapters/06_data_analysis.html#zonal-statistics-with-two-images
The second parameter should be a zone image with discrete values. I don't think your croplands image is the right input.

Hi Prof.Wu, thank you very much for your quick response. I recreated an image of gridded croplands with discrete values. Each value of the single band represents a zone of the grid cell. The image of croplands includes 270000 grids. However, it encountered the same error. Is it because of too many grid cells that exceeds the computing limits of GEE? I am really grateful for your help.

This function is intended for raster images with a limited number of discrete values, like land cover data with 10-30 classes. It will not work for an image with tens of thousands of discrete values. You will have to design your own algorithm to overcome the GEE limit.

Thank you for your recommendation.


Support multi-nameservices uri for creating HDFS fileSystem instance

Feature Introduction
Currently, when we use HDFS Command Line to access URL that is Alluxio style,  it can be like this:
hdfs dfs -ls alluxio:///user/xxxx.
The command-line above does not support multiple alluxio cluster in the same time. So, the goal of this issue is to support such feature.
After applying this patch , we can use hdfs dfs -ls alluxio://ns1/user/xxx , hdfs dfs -ls alluxio://ns2/user/xxx and so on in the same HDFS Client environment， where ns1 and ns2 are different alluxio cluster.
This patch also takes compatibility into account，if the uri does not have authority, it will fall back to original implementation.
How to Use?
Suppose that we want to use two alluxio cluster which are named "ns1"  and "ns2" in HDFS command-line . We need to add new configuration entries below  to hdfs-site.xml:

<property>
    <name>alluxio.ns1.zookeeper.enabled</name>
    <value>true</value>
</property>

<property>
    <name>alluxio.ns1.zookeeper.address</name>
    <value>your ZK cluster address</value>
</property>

<property>
    <name>alluxio.ns1.zookeeper.election.path</name>
    <value>/alluxio/ns1/election</value>
</property>

<property>
    <name>alluxio.ns1.zookeeper.leader.path</name>
    <value>/alluxio/ns1/leader</value>
</property>

<property>
    <name>alluxio.ns2.zookeeper.enabled</name>
    <value>true</value>
</property>

<property>
    <name>alluxio.ns2.zookeeper.address</name>
    <value>your ZK cluster address</value>
</property>

<property>
    <name>alluxio.ns2.zookeeper.election.path</name>
    <value>/alluxio/ns2/election</value>
</property>

<property>
    <name>alluxio.ns2.zookeeper.leader.path</name>
    <value>/alluxio/ns2/leader</value>
</property>

The below picture displays results in product.

similar to #14021?

similar to #14021?

Hi, @qian0817 . I think it is not similar with #14021 , because this patch focuses on multiple alluxio clusters, not only one HA alluxio cluster.

You can specify alluxio service with URL authority like hdfs dfs -ls alluxio://zk@host:2181/path and hdfs -ls alluxio://host:19998/path. Releated doc is here.

You can specify alluxio service with URL authority like hdfs dfs -ls alluxio://zk@host:2181/path and hdfs -ls alluxio://host:19998/path.
In addition, you can use hdfs --confg [config path] dfs -ls alluxio:/// or hdfs dfs -D[conf key]=[conf value] -ls alluxio:///  to specify config.

Hi, @qian0817 . sry to reply too late.  I  have watched your code and doc,  it's very nice. In fact, our goals is similar. You have extended both master.rpc and zookeeper.enable, I think my solution is a specific supplement in zookeeper.enable sence？

I'll come back to review if this should be added or not after #14021

I'll come back to review if this should be added or not after #14021

@ZhuTopher ,  thx a lot !

@hfutatzhanghb Could you give an example config for raft based embedded journal ha?


codeActionsOnSave "source.fixAll" removes used imports

Type: Bug
Having "source.fixAll" in my "editor.codeActionsOnSave" frequently deletes used (not unused) imports on save, especially if they're unsorted.
I haven't found a reliable way to reproduce this yet. But if I remove  "source.fixAll" from code actions, all is well.
// settings.json
"[python]": {
  "editor.codeActionsOnSave": [
    "source.fixAll",
    "source.organizeImports",
  ],
},

Extension version: 2022.12.0
VS Code version: Code 1.70.1 (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:08:46.959Z)
OS version: Darwin arm64 21.6.0
Modes:
Remote OS version: Linux x64 3.10.0-1160.71.1.el7.x86_64

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
5, 5, 5

Memory (System)
16.00GB (0.08GB free)

Process Argv
pmg --crash-reporter-id c13bf5eb-cd11-4709-908c-c293aee75f36

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: csd3

OS
Linux x64 3.10.0-1160.71.1.el7.x86_64

CPUs
Intel(R) Xeon(R) Gold 6142 CPU @ 2.60GHz (64 x 2600)

Memory (System)
187.36GB (161.14GB free)

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
pylanb8912cf:30529770
vsclangdc:30486549
c4g48928:30535728
hb751961:30543456
dsvsc012:30540252

@janosh Can you try installing the https://marketplace.visualstudio.com/items?itemName=ms-python.isort extension and see how it works for you in this scenario.

That seems to help! I need to keep a watch on this to say for sure. Thanks for the pointer!
Is that extension temporary? I.e. aimed at being merged back into vscode-python? I'd rather not have yet another extension. I also don't understand why isort needs special treatment. VS Code uses the environment installed black just fine but bundles its own isort IIUC?

That will likely be the way we ship various tool support in the extension. The reason we are doing this is to allow easier external tool support. Also, shipping these tools as separate extension allows us to bundle them (so no need to install), provide deeper integration with the tools. For example, in the isort extension, we do a --check run on all open files and report improper sort as error, the extension also provides a quick fix for such errors. Such integration is not easy in the core python extension, and requires Typescript knowledge, but in the isort extension all of that is achieved purely in python code.
We have extensions for black and pylint. we are currently working on flake8 and autopep8 for this milestone. We also have a template that allows you to build and ship your own tools as extension on your own.
Here is more context from Brett on why we are going this way: https://twitter.com/brettsky/status/1555632119312879616

I see. Thanks for explaining!
If I may voice a small concern with this approach, it sounds like having each formatter and linter bundled with its own VS Code extension makes it harder to reproduce your local setup in CI.

The extension provide a way to configure where they load the tool from. So, by default those extension will use the one that is bundled. You can change the importStrategy setting to have it load from your environment instead.
Closing this for now, if you do run into issues with the isort extension please file a bug on the isort extension repo.

Can we just disable this setting?  It's very jenky!    This was a very poor decision!

@ericmeadows Of course you can disable it. Just remove "source.fixAll" from your "editor.codeActionsOnSave".
But I have to agree, in further testing it has been quite janky, likely to delete occasional lines of code during formatting.


Certain ASG metrics not supported

Hallo!
The enabledMetrics property of the autoscaling.Group class allows us to enable which metrics we want to enable for an autoscaling group.
In the documentation it states the following are allowed values:

GroupDesiredCapacity
GroupInServiceCapacity
GroupPendingCapacity
GroupMinSize
GroupMaxSize
GroupInServiceInstances
GroupPendingInstances
GroupStandbyInstances
GroupStandbyCapacity
GroupTerminatingCapacity
GroupTerminatingInstances
GroupTotalCapacity
GroupTotalInstances

However, if we take a look at the source of the enum or the constant definitions for Metric you'll notice only 8 ASG metrics are actually supported (out of the 13).
Specifically, these are missing:

GroupInServiceCapacity
GroupPendingCapacity
GroupStandbyCapacity
GroupTerminatingCapacity
GroupTotalCapacity

This is easily confirmed locally because attempting to use one of the "missing metrics" causes an error in VS Code:

Hoping this is an easy fix and I'm more than happy to submit a PR if needed. Either way, let me know if you require any further information!

Hi @jhinklew
Thanks so much for opening this - a PR is on the way to fix this up!
Paul


Ansible request for qemu on risc-v build machines

[ ] Request for new playbook addition

Details:
Currently the risc-v UMA builds do not require qemu in order to build. However, porting the build over to CMake is considerably easier if qemu is installed.

There are 2 sets of executables that cause issues.

[hook/trace]gen. Technically there is no reason that we can't compile these for the build machine (which is what the UMA builds currently do), however its much more compilcated in cmake. Unlike autotools which allows you to have a BUILD_C[XX]toolcahin separate from the normal c/c++ toolchain, cmake only supports a single c/c++ toolchain. The official way of supporting build tools on cmake is to run cmake twice. Once to compile the build tool and again for the actual build. Doing this in the openjdk build is a hassle, especially given the second point.

constgen. Due to the nature of of constgen it needs to be compiled for the target arch. The risc-v uma build side steps the issue of  not having qemu by simply not building or running costgen. This works for the moment since we dont have any risc-v assembly code in openj9. However, it seems inevitable that will change in the future.

I've been given a statically linked qemu for the purposes of testing this. It looks like a change was made to require the statically linked qemu and so the builds have been failing for us since that went in so the builds (restricted access) have bene failing since October.
I've put in a PR to pull a suitable qemu during the build process, so that should stabilise the builds again going forward.


Ensure wasmvm static library version matches wasmv import in go.mod

Currently we import wasmvm 1.4.0 in our go.mod while we statically link against 1.2.4 in our dockerfile, Would be good to ensure these are always in sync.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

I think we can maybe just fetch the value from our go mod, and add it as a build arg to the wasm dockerfile.
lib_version="$(modules/light-clients/08-wasm/go.mod | grep "github.com/CosmWasm/wasmvm" | awk '{print $NF}')"
docker build ... --build-arg LIB_VERSION=${lib_version}

Or use a sane language like python :D

pls

Ah, we did have a small TODO in the dockerfile that offers a nicer approach:

TODO: nice to have: a script to download version matching the wasmvm version in go.mod.

that way it'll automatically be handled for us

how do we assign @TODO to do it for us

You can do this just like wasmd:

https://github.com/CosmWasm/wasmd/blob/v0.41.0/x/wasm/module.go#L314-L326
https://github.com/CosmWasm/wasmd/blob/v0.41.0/x/wasm/module.go#L286-L301

Thank you @webmaster128 , I added your suggestion to our simapp too!

ref #4837


Upload multiple and get responses in an array

Hi,
I am using the ng-file-upload (multiple) with my angular js project with node js on the backend.
I have made an api on node js to upload the files and then return back some data in the json format. For a single I am able to get the data. But if i upload multiple files, I am not getting. Am I doing anything wrong?
HTML:
Upload
Controller:
$scope.uploadFiles = function (files) {
var upload = Upload.upload({url: "URL",
data: {file: files},
arrayKey: '[i]'});
upload.then(function(resp) {
// file is uploaded successfully
debugger
//Not Getting Array of resp.data
//console.log('file ' + resp.data.filename + ' is uploaded successfully. Response: ' + resp.data);
}, function(resp) {
// handle error
}, function(evt) {
// progress notify
//console.log('progress: ' + parseInt(100.0 * evt.loaded / evt.total) + '% file :'+ evt.data.filename);
});
}

Could be the way you read the file on the server. Btw arrayKey default value is [i] so you can remove it

Thanks Danial, I was making a mistake in the Api. It was returning a single response. Fixed it.


🐛 noUnusedImports removes React import unsafely

Environment information
CLI:
  Version:                      1.3.1
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.6.1"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/8.9.2"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?
The nursery.noUnusedImports rule currently removes the import React from 'react' import in React projects (.tsx/.jsx files) when it's not directly used. This is not a safe thing to do. Although some postprocessors (like Next.js) handle this fine, others like jest and vitest will fail with:
ReferenceError: React is not defined
 ❯ ui/Alert/Alert.test.tsx:14:32
     12|
     13|  it('should render with only a title', () => {
     14|   const { getByText } = render(<Alert title='Hello World' />);
       |                                ^
     15|   expect(getByText('Hello World')).toBeDefined();
     16|  });

This is because JSX syntax is transpiled to React.createClass under-the-hood.
Expected result
Ideally Biome would leave import React from 'react' imports alone if there is JSX syntax in the file. If that's not possible, maybe it's better to add an exception to the react module for now?
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Although some postprocessors (like Next.js) handle this fine, others like jest and vitest will fail with:

In many cases, this is due to a lack of bundler or transpiler settings.
If you use vitest with React, you need to use vitejs/plugin-react
ref: https://github.com/vitest-dev/vitest/issues/1572#issuecomment-1170883252
If you use jest, you need to pass some options in transpiler settings.
Babel: https://babeljs.io/docs/babel-preset-react#both-runtimes
SWC: https://swc.rs/docs/configuration/compilation#jsctransformreactruntime

I am unsure about the course of action here. I think we will wait to gather more feedbacks.

If you use vitest with React, you need to use vitejs/plugin-react

Ah! That's a great point. That works for me.
I think I'll close this issue now as my specific problem is resolved with that solution.

@Conaclos we hit this today too. It is safer for us not to be forced to remove the imports. Can there be an option setting for the rule to ignore this import?

We have a non-editable company-wide webpack and TS configs, and we can't remove React import.
Is there a possibility to add an option to preserve React imports?


Unexpected error pops up in the console when attach a running python.exe

Environment

Steps to Reproduce
1.Launch VS and create new python application
2.Add an input('>') or raw_input('>') at the top of your code - depends on version of python
3.Add some more python code after that with breakpoint(s)
4.Start WITHOUT debugging
a. Console will wait for you to input something
5.Debug > Attach to Process, select the appropriate python.exe (easiest if there's only one, you may want to close interactive windows first)
6.Type enter in the console
7.Check that it stops at the breakpoint
Expected behavior
It stops at the breakpoint without any errors
Actual behavior
The cmd console shows this

Additional context and screenshots

Sample Code
input('>')

from math import cos, radians

# Create a string with spaces proportional to a cosine of x in degrees

def make_dot_string(x):

    rad = radians(x)                             # cos works with radians

    numspaces = int(20 * cos(radians(x)) + 20)   # scale to 0-40 spaces

    st = ' ' * numspaces + 'o'                   # place 'o' after the spaces

    return st

def main():

    for i in range(0, 1800, 12):

        s = make_dot_string(i)

        print(s)

main()

On today's environment

Still failed to hit the breakpoint and an error dialog displayed at the end of the attach.

Does it make any difference if you do import threading in the script?

@int19h
on today's build, i can repro these two phenomena ,though i do  'import threading' in the script

Situation1（the breakpoint is hit）

Situation2(the breakpoint isn't hit)

NOTE:
The operation steps are the same in both situation, the only difference is that the waiting time is different before Type  enter in the console(situation1 is typing enter after waiting some seconds, situation2 is typing enter immediately)

Without import threading, the warning printed to console is expected. Note that it must be imported before you attach (i.e. before input())!.
The error message box you sometimes get with import threading about server failing to attach appears to be a timing issue. Attach-to-PID is inherently asynchronous as it has to inject itself into a running Python thread using Py_AddPendingCall. It is entirely possible for the app to run to completion before the pending call is actually processed by the runtime, at which point the app exits while PTVS is still waiting for the injected code to connect back to it. There's nothing we can really do here as we don't have control or even insight over the debuggee until injection actually completes. This is usually not an issue in practice because attach-to-PID is normally used to attach to long-running processes; in this case, you can simulate it by calling main repeatedly in  a loop, and in that repro, the breakpoint is consistently hit as espected.


fix(logging): Fixed string formats in Selflog.WriteLine calls.

Fixes #381

Thank you for the find and fix. ❤


Let's Go

Tellie PR Checklist

[ ] I have run QA Wolf PR Checks
[ ] I have run Chromatic Checks
[ ] I have added meaningful commit messages

/fast-forward


openmessaging benchmark is functional for Artemis ?

I see a repo already there for artemis-driver :
https://github.com/openmessaging/benchmark/blob/master/driver-artemis/
If someone has already run performance tests using openmessaging benchmark any help would be much appreciated?

@achinjain214 this project is related to the operator, while your request is related to the operand Apache ActiveMQ Artemis, see https://github.com/apache/activemq-artemis


PowerToy stuck when exiting Zoom breakout room

ℹ Computer information

PowerToys version: 0.31.2
PowerToy Utility: Fancy Zone
Running PowerToys as Admin: Yes
Windows build number: 20H2 (OS Build 19042.844)

📝 Provide detailed reproduction steps (if any)

Be in a Zoom meeting as an attendant (e.g. a lesson)
Join breakout rooms
Leave breakout rooms (which starts in full screen by default) when it's about to end
Repeat step 2 and step 3 for 2 to 3 times
Now Fancy zone stops working, and trying to click PowerToy tray icon is also not responsive

✔ Expected result
Fancy zone keep working
❌ Actual result
Now Fancy zone stops working. Pressing shift does not show the hint, and the keyboard shortcut is also not working.
And trying to click PowerToy tray icon to see what is going on is also not responsive. The only way to get it back is to force quit it and open it again.
📷 Screenshots
(I lost the screenshot of Task Manager saying PowerToy is using more than 10% resource. I will add it tomorrow)

hmm cannot reproduce anymore i will reopen this when i can......

Sorry it took a while, but finally able to reproduce it again in 0.33.1

Hi @louis993546, have you updated to the latest version in the mean time, and is this issue still occuring?

Hi @louis993546, have you updated to the latest version in the mean time, and is this issue still occuring?

I am lucky enough to not have to use zoom anymore, and I haven't been able to reproduce it in other ways. Feel free to close it.


fix issue that open tracing activation set tag failed

Coverage decreased (-0.1%) to 49.065% when pulling 26fdf8599824ecea1a1b79392fd9235243074700 on ascrutae:zhangxin/fix/ot-set-tag-failed into 79a45823b686c970a294712c7b4b0a91cef02dc4 on wu-sheng:master.

Coverage decreased (-0.1%) to 49.065% when pulling 91d08bbcd92aefdaa44caff19100aae41fcfa24e on ascrutae:zhangxin/fix/ot-set-tag-failed into 79a45823b686c970a294712c7b4b0a91cef02dc4 on wu-sheng:master.


Update Bazel to latest as at Mar 2020 (2.2.0)

Description
Requires rebuilding the AMI, and doing brew upgrade bazelbuild/tap/bazel locally.

At latest (3.0.0) now


Update menu items in Community header

I noticed the publications link is dead. I don’t understand why the links test didn’t catch it, it’s exactly the kind of problem it’s for.
While checking that, I realised that the main site’s navigation has changed, and Publications and Events have gone, and Roadmap has appeared. So I've mirrored that into the navigation here.

This just hit my inbox... weird. yes, remove publications as it's a dead page.


Publish dialog doesn't remember the VM I most recently published to.

2 minutes ago, I published to an instance called hello-aspnet.  But when I publish again the dialog has forgotten my choices:

Sub-issue of #863

Now being tracked as part of #863.


13 Pro Max iOS 15.7.2 Misaka 8.0.1/2/3/4/5/6/7/8/9，TIPS are all gray, unable to enter KFD mode and restart repeatedly

se2 15.7.2 So do i

13 pro  15.7.2  ,so do I.


fix: fix os version check in modal header

The type of this PR is: fix
This PR resolves CX-1268
Description
Our os version check in the consignments flow was faulty and trying to coerce a version string "14.4.1" into a number which resulted in NaN. This uses an osMajorVersion util instead that parse the version correctly, also moved this to platfromUtil file because it feels like it fits there a bit better.
Screenshots

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

nice catch!


JsonField can't resolve dot notation for source parameter

What did you want to do
I wanted to pass a dot notation string to JsonField component
<JsonField source="source.nested" />
What did you expect
I expected to have my nested component displayed correctly
What happened instead
It displays "root":{}
I don't know if this a bug, a upcoming feature or a wanted behavior, but the strange thing is that I have no problem with the JsonInput component using dot notation.

Hi @fbigand thanks for reporting this bug.
It should be fixed in this new release: https://github.com/MrHertal/react-admin-json-view/releases/tag/v1.0.4

Thank you for your response!
I installed the new release (1.0.4), but unfortunately the problem is not solved on my side. I tested with both nested object and nested array, but none of them work (I don't know if they are handled differently).
I used this object for the test:
{
    ...
    "content": {
        "test_array": [
            1,
            2,
            3,
            4
        ],
        "test_object": {
            "test": "test"
        }
    }
}

And I called JsonField like this inside my Show view:
...
<Tab label="Content">
    <JsonField source="content.test_array" />
    <JsonField source="content.test_object" />
</Tab>
...

Both of them render an empty json.

Thanks for your response.
It would be interesting to know what your content field looks like after react-admin gets the data.
Could you show the log of the record at this point? You can use a function field like this:
import { FunctionField } from 'react-admin';

<FunctionField
  label="Test"
  render={(record) => {
    console.log(record);

    return <JsonField source="content" record={record} />;
  }}
/>

I would like to know if your content field is a string like this:
content: "{"test_array":[1,2,3,4],"test_object":{"test":"test"}}"
Or if it is an already parsed nested object like this:
content:
  test_array: Array(4)
    0: 1
    1: 2
    2: 3
    3: 4
    length: 4
    __proto__: Array(0)
  test_object:
    test: "test"
    __proto__: Object
__proto__: Object

The console.log displays the record that wraps the "content" attribute, and it is displayed as Javascript object.
{…}
  content: {…}
    test_array: (5) […]
      0: 0
      1: 1
      2: 2
      3: 3
      4: 4
      length: 5
      <prototype>: Array []
    test_object: {…}
      test: "test"
      <prototype>: Object { … }
    <prototype>: Object { … }
  id: 12
  title: "Some title"
  <prototype>: Object { … }

This is weird, I could not reproduce. Here is what I tried:
import { SimpleShowLayout, FunctionField } from "react-admin-json-view";
import { JsonField } from "react-admin-json-view";

<SimpleShowLayout>
  <FunctionField
    label="content.test_array"
    render={(record) => {
      const flowParams = JSON.parse(record.flowParams);
      console.log(flowParams);

      return (
        <JsonField
          source="content.test_array"
          record={{ ...record, content: flowParams }}
        />
      );
    }}
  />
  <FunctionField
    label="content.test_object"
    render={(record) => {
      const flowParams = JSON.parse(record.flowParams);
      console.log(flowParams);

      return (
        <JsonField
          source="content.test_object"
          record={{ ...record, content: flowParams }}
        />
      );
    }}
  />
</SimpleShowLayout>

On my project, flowParams field is a JSON string that has this value: {"test_array":[1,2,3,4],"test_object":{"test":"test"}}.
In order to be as close as possible to your case, I parsed this value and set the result to record.content.
console.log(flowParams); is printing:
{test_array: Array(4), test_object: {…}}
  test_array: (4) [1, 2, 3, 4]
  test_object: {test: "test"}
  __proto__: Object

As a result, I got this:

Can you check the difference with your code?
Did you restart your project after upgrading this package? (sorry I have to make sure 🙂)

Thank you for your last remark, because it is most probably that the package was not updated inside the docker container that is running the application.
Now the problem is solved and it works perfectly. So thank you for the update.

Thank you for your last remark, because it is most probably that the package was not updated inside the docker container that is running the application.
Now the problem is solved and it works perfectly. So thank you for the update.


[BitSail][Components] csv deserialization would fail when delimiter's length is more than 1 (e.g. "##")

Describe the bug
When setting CsvReaderOptions.CSV_DELIMITER as “##” which cause csv delimiter's length more than one, it will fail on running deserializationSchema.deserialize() function.
To Reproduce
Adding below test case into CsvDeserializationSchemaTest, to run test can reproduce the problem.
@Test
public void testCsvMultiDelimiterReplaceChar() {
    BitSailConfiguration jobConf = BitSailConfiguration.newDefault();
    jobConf.set(CsvReaderOptions.CSV_DELIMITER, "##");
    TypeInfo<?>[] typeInfos = {TypeInfos.STRING_TYPE_INFO, TypeInfos.INT_TYPE_INFO};
    String[] fieldNames = {"c1", "c2"};
    String csv = "star##2222";
    CsvDeserializationSchema deserializationSchema = new CsvDeserializationSchema(jobConf, typeInfos, fieldNames);
    Row row = deserializationSchema.deserialize(csv.getBytes());
    Assert.assertEquals(row.getField(0).toString(), "star");
    Assert.assertEquals((int) row.getField(1), 2222);
}

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Test Environment
Describe the environment where the test project was build.

OS [Windows]
JDK [1.8.0_331]
Maven [3.8.6]
...

Additional context
By debugging the code, it seems that lack of valid replacement ("##" -> "§") for input byte array is the result.
Moreover, name of testCsvDeltmiter() function in CsvDeserializationSchemaTest class seems mistyped, it is supposed to be testCsvDelimiter().

@Jake-00 Thanks for you issue, we already got your issue, do you have any interest to fix this issue?

@hk-lrzy Sure, I'm willing to fix it.

Hi @Jake-00, thanks for your contribution to the BitSail community. Would you like to join contributor chat group? Here is the QR code. If it expires, you can leave a message here. Look forward to your coming!


builder: Add AppArmor to runc buildtags for armhf - fixes #27351

I update the builder cconfiguration for debian and raspbian on armhf to include the apparmor (and incidentally the selinux) build tags in order for runc to be build with the correct dependencies.
This fixes #27351 for Debian and Raspbian, and should be taken together with PR #27327 for the Ubuntu Trusty platform.
I did build the Raspbian deb package on my Raspberry Pi. It builded successfully and when testing issue #27351 it was resolved. This was not tested on Debian or Ubuntu on armhf, but this is expected to work as well.
Commit message:
On Raspbian and Debian Jessie for ARMv7 (aka armhf), the builtags for runc
were missing. These buildtags should include 'apparmor' and 'selinux'.
Signed-off-by: Jean-Christophe Berthon<EMAIL_ADDRESS>

Can you change this PR to merge into the master branch not 1.12 please. If there is going to be a 1.12.3 release we will cherry-pick PRs into that branch later, but we only accept PRs to master.

Hi @justincormack
I've tried to simply change the target branch from 1.12.x to master, but I ended up with a lot of "commits" that should be merged. I guess you could cherry pick mine in the list, but I guess it is easier for you to have a single commit in the PR.
So I will close this PR an re-open a new one, with only the required commit and against your master branch. Sorry for the confusion.


Helper interfaces

This adds 3 interface files, useful for helper apps. These are a very early stage, and still need to be completed.

this repo no longer being used for api development


calculate_average

Hi! I would like to start working on the calculate_average: Calculates the average of two numbers function.

Hi everyone! I sent a pull request( #11 ), could please someone review my function?


Introspection Query not being run

Version and Environment Details
Operation system:  macOS High Sierra
IDE name and version: WebStorm 2018.2.3
Plugin version: 1.7.2
Expected Behaviour
Introspection Query should be run and schema file should be updated.
Actual Behaviour
Nothing happens.
Steps to Reproduce / Link to Repo with Reproduction and Instructions
I was using a local schema file, but I switched to using the introspection query to save me having to update the schema file every time there was a change.
My graphql.config.json file:
{
  "schema": {
    "request": "[...]/graphql",
    "method": "POST",
    "postIntrospectionQuery": true
  },
  "endpoints": [
    {
      "name": "API",
      "url": "[...]/graphql"
    }
  ]
}

The console output:
/usr/local/bin/node --no-deprecation "/[...]/Application Support/WebStorm2018.2/js-graphql-intellij-plugin/js-graphql-language-service.dist.js" --port=51815
JS GraphQL listening on http://<IP_ADDRESS>:51815/js-graphql-language-service
Setting Project Dir '/[...]'
Watching '/[...]/graphql.config.json' for changes.

I've tried pressing the "Restart JS GraphQL Language Service" button but nothing seems to happen.

Hi Tam.
Thanks for using the plugin.
The "request" configuration field is expected to be an object. See https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/blob/32d6739161077e95cc2b91937cb221c3553ee2ee/resources/META-INF/graphql.config.json#L10-L20
I'm closing this but feel free to comment if this doesn't resolve the issue.

Ahhh yep, thanks!


Cannot startunity into trusty.

I ran
 sudo startunity
the output was
X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-76-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.8.11 #1 SMP Mon Aug 31 19:53:26 PDT 2015 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=4453db81-7fc7-9443-b1b3-dedc142b0b9e/PARTNROFF=1 hashtree=PARTUUID=4453db81-7fc7-9443-b1b3-dedc142b0b9e/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=38da5d8e079de303288a85e0420d1c7c60982e4f salt=112a1747e8b7f41d4e33d23397566bb755fb91abb8efd7da23a3130110a76a28" noinitrd vt.global_cursor_default=0 kern_guid=4453db81-7fc7-9443-b1b3-dedc142b0b9e add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic iTCO_vendor_support.vendorsupport=3
Build Date: 12 February 2015  02:49:29PM
xorg-server 2:1.15.1-0ubuntu2.7 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.30.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Fri Sep 11 14:31:59 2015
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
Unable to set master
xf86: found device 0
xf86: found device 0
crouton: version 1-20150827155505~master:edbce112
release: trusty
architecture: amd64
xmethod: xorg
targets: unity,extension
host: version 7262.52.0 (Official Build) stable-channel peppy
kernel: Linux localhost 3.8.11 #1 SMP Mon Aug 31 19:53:26 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
No Chromium OS X server is available.
Cannot open /sys/class/tty/tty0/active: No such file or directory
Error: target STRING not available
(II) AIGLX: Suspending AIGLX clients for VT switch
^C
Session terminated, terminating shell.../usr/bin/xinit: connection to X server lost

waiting for X server to shut down Hangup
Hangup
Hangup
Running exit commands...
(EE) Server terminated successfully (0). Closing log file.

/usr/bin/xinit: unexpected signal 2
 ...terminated.
Unmounting /mnt/stateful_partition/crouton/chroots/trusty...
Sending SIGTERM to processes under /mnt/stateful_partition/crouton/chroots/trusty...
Sending SIGKILL to processes under /mnt/stateful_partition/crouton/chroots/trusty...

(the chroot started but was a black screen. I hit crlt c)
so I ran
 sudo sh crouton -u -n trusty -t core -t unity
output:
/usr/local/chroots/trusty already exists; updating it...
Preparing chroot environment...
Installing brightness into the chroot...
Installing croutonpowerd into the chroot...
Installing croutonversion into the chroot...
Installing host-dbus into the chroot...
Installing host-x11 into the chroot...
Installing volume into the chroot...
Installing pulseaudio-default.pa into the chroot...
Installing croutoncycle into the chroot...
Installing croutontriggerd into the chroot...
Installing croutonxinitrc-wrapper into the chroot...
Installing setres into the chroot...
Installing xinit into the chroot...
Installing xbindkeysrc.scm into the chroot...
Installing xorg-intel-sna.conf into the chroot...
Installing xserverrc into the chroot...
Installing xserverrc-xorg into the chroot...
Installing xserverrc-local.example into the chroot...
Installing startunity into the host...
Installing crouton-noroot into the chroot...
Installing startunity into the chroot...
Installing gnome-session-wrapper into the chroot...
Installing crouton-unity-autostart into the chroot...
Installing unity-autostart.desktop into the chroot...
Installing unity-profiled into the chroot...
Installing croutonclip into the chroot...
Installing croutonnotify into the chroot...
Installing croutonurlhandler into the chroot...
Installing enter-chroot into the host...
Installing delete-chroot into the host...
Installing edit-chroot into the host...
Installing mount-chroot into the host...
Installing unmount-chroot into the host...
Installing crash_reporter_wrapper into the host...
Installing target core...
Preparing environment...
Preparing software sources...
 Done
W: GPG error: http://ppa.launchpad.net trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 10F47D907D103299
Ensuring system is up-to-date...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
sudo is already the newest version.
apt-transport-https is already the newest version.
wget is already the newest version.
ca-certificates is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Generating locales...
  en_US.UTF-8... up-to-date
Generation complete.
Generating locales...
  en_US.UTF-8... up-to-date
Generation complete.
Syncing timezone...
Installing target audio...
Fetching CRAS (branch 4ba75473020144f2920eb09fb1c70f1e6c0ee067)...
--2015-09-11 14:38:00--  https://chromium.googlesource.com/chromiumos/third_party/adhd/+archive/4ba75473020144f2920eb09fb1c70f1e6c0ee067.tar.gz
Resolving chromium.googlesource.com (chromium.googlesource.com)... <IP_ADDRESS>, 2607:f8b0:400d:c03::52
Connecting to chromium.googlesource.com (chromium.googlesource.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: '/tmp/crouton-cras.K3DrUz/adhd.tar.gz'

     0K .......... .......... .......... .......... .......... 93.5K
    50K .......... .......... .......... .......... ..........  253K
   100K .......... .......... .......... .......... ..........  146K
   150K .......... .......... .......... .......... .......... 91.9K
   200K .......... .......... .......... .......... ..........  105K
   250K .......... .......... .......... .......... .......... 89.4K
   300K .......... .......... .......... .......... .......... 61.0K
   350K .......... .......... .......... .......... ..........  367K
   400K .......... .......... .......... .......... ..........  155K
   450K .....                                                  66.4K=4.0s

2015-09-11 14:38:07 (113 KB/s) - '/tmp/crouton-cras.K3DrUz/adhd.tar.gz' saved [466492]

Reading package lists... Done
Building dependency tree
Reading state information... Done
alsa-utils is already the newest version.
libasound2:i386 is already the newest version.
libspeexdsp1:i386 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
gcc is already the newest version.
gcc-multilib is already the newest version.
pkg-config is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libc6-dev : Breaks: libc6-dev:i386 (!= 2.19-0ubuntu6.6) but 2.19-0ubuntu6 is to be installed
 libc6-dev:i386 : Depends: libc6:i386 (= 2.19-0ubuntu6) but 2.19-0ubuntu6.6 is to be installed
                  Depends: libc-dev-bin:i386 (= 2.19-0ubuntu6)
                  Depends: linux-libc-dev:i386 but it is not going to be installed
                  Breaks: libc6-dev (!= 2.19-0ubuntu6) but 2.19-0ubuntu6.6 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/trusty...

please help,
I don't want to delete this chroot.

sudo enter-chroot works

Rebootted computer.
ran sudo startunity
took a while but eventually worked


AutoDock ..bug issue

Unable to open and run Autodock from last 4-5 months.
Sometimes it works well but after 1or 2 dock process it suddenly stops working.
Now I am getting this problem to much..... Showing

Contact to application support team.
Attribute error: set user preference instance has no attribute 'form'.
Hit enter to continue.....after this all windows suddenly closes and not allow autodock GUI to open.

Autodock is a majorly used tool for my work and due to this problem my work is so much affected. Require solution urgently.

What is robot? Can you explain it in detail and what is its role in doing
docking?
On Wed, Dec 7, 2022, 18:30 Morgan Quigley @.***> wrote:

I'm not sure I understand steps 1-3. What type of robot are you using?
—
Reply to this email directly, view it on GitHub
https://github.com/osrf/autodock/issues/13#issuecomment-1340931366, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A263PKTEZY23OAMT22BF2FLWMCC63ANCNFSM6AAAAAASWQZKPE
.
You are receiving this because you authored the thread.Message ID:
@.***>

If I am not doing mistake this is about ligand protein docking tool- Auto
Dock from Scripps
research institute.
On Wed, Dec 7, 2022, 18:37 Morgan Quigley @.***> wrote:

Closed #13 https://github.com/osrf/autodock/issues/13 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/osrf/autodock/issues/13#event-7977629458, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A263PKUSCNGBEGZKHYBXMYTWMCDYTANCNFSM6AAAAAASWQZKPE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh.. thank you for reply and clearing confusion.
On Wed, Dec 7, 2022, 18:49 Morgan Quigley @.***> wrote:

No, this is a robotics software framework; it has nothing to do with
biology. A different definition of "auto dock" 😄
You might want to try this repo
https://github.com/ccsb-scripps/AutoDock-GPU instead, or other repos
inside the ccsb-scripps https://github.com/ccsb-scripps GitHub
organization. Cheers
—
Reply to this email directly, view it on GitHub
https://github.com/osrf/autodock/issues/13#issuecomment-1340958075, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A263PKWRISGXWZJWKLAVR53WMCFGNANCNFSM6AAAAAASWQZKPE
.
You are receiving this because you authored the thread.Message ID:
@.***>


connectionProfile.yaml -> networkConnection.yaml

Signed-off-by: Saurabh0707<EMAIL_ADDRESS>

Thank you for your contribution, the Fabric repository uses Gerrit for source control, this GitHub repo is only a mirror. Please see our contribution doc to learn how to submit Change Requests via Gerrit.
https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html

@btl5037 , Sure. I'll learn contibuting over gerrit.


Clarify schedule time format

I notice the GMT is removed on session time, but I got confused about it. What time the Sessionize API returned? What time the website displayed? GMT or user's local time? It will be better to convert the time to the user's timezone if possible.

@greyli see the mail i cced you. Apparently it gets displayed to the speaker's timezone but now checking no ... i guess we must readd GMT

OK, I'm gonna re-add the GMT first, then try to support timezone convert based on the user's timezone.


add submissionType for Editorial stream and SoTM in output

Description
Please add a new submissionType value for the Editorial stream (created by RFC 9280).
For "Status of This Memo" content when rendering an RFC, please see item 25 ("Editorial Stream Informational") on this page:  https://www.rfc-editor.org/materials/status-memos.txt
which is the outcome of S6.3 of RFC 9280.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

This will also be relevant to the bibxml-service when enacted.

Here is an additional nudge for this simple addition. I am being blocked from submitting a draft in the Editorial stream because of this.

Has a draft been adopted by the RSWG? If not, why would you need to indicate editorial stream in the document at this time?
In any case, this will be a high priority, but because of vacations it will be next week at the earliest.

(There is also a lot of work underway to build out the parts of the datatracker that would let the RSWG adopt a document, request publication, and track RSAB approval).

Has a draft been adopted by the RSWG? If not, why would you need to indicate editorial stream in the document at this time?

I wanted to be sure that it could be adopted before I suggest to the WG that it should be.


Add support for "newTabPosition" API

https://bugzilla.mozilla.org/show_bug.cgi?id=1344749 was fixed today; I'm wondering if this add-on should use the new API to control new tabs position.

This patch implements the preference "browser.tabs.insertAfterCurrent" which,
when set to true, will cause all tabs (related and unrelated) to be opened next
to the current tab.

It also implements the browserSettings API "newTabPosition", which allows
extensions to control both "browser.tabs.insertRelatedAfterCurrent", and
"browser.tabs.insertAfterCurrent" via values for "afterCurrent",
"relatedAfterCurrent" and "atEnd".

No, the new preference makes this extension obsolete. But thanks for keeping me updated on this.

@sblask The new browser.tabs.insertAfterCurrent preference has been added to Firefox 61.0, released today.


Log level configurable?

Hi,
I find the logging to /var/log/ykval.log (for the Validation server) and /var/log/auth.log (KSM, per the current out-of-the-box config) extremely verbose, and this might expose more info than desired in logs, even in relatively secured servers.
E.G the KSM appears to log 'plaintext' values post-decryption, not sure how sensitive but it raises alarm bells
Is there any way to configure the verbosity level in the config.php files in /etc/yubico/(val or ksm)/* ? I can't seem to find any sample configuration or documentation that states it's possible (without modifying the PHP directly)
Thanks

I would appreciate a configuration option in config.php.
Decrease logging into syslog is easy, but modern systems have journald and the service should normally not log that much into journald.


How to login?

I am new to clerk and using elysia for backend, and was wondering how to login with clerk, or open clerk login page in elysia.  (I dont have any frontend). The example only shows how to check if user is logged in or not.

You can check the example here - https://github.com/wobsoriano/elysia-clerk/tree/main/dev
Feel free to reopen


Include npub/nsec format when printing keys

Extend the console output to include the keys in npub/nsec format.
This format is used by some Nostr apps because it's better UX^1 than the keys in hex. The prefix makes it clear to the user which key it is (the public or the secret one).
Conversion (back to hex) can be checked with https://damus.io/key/

thanks! LGTM


Add protobuf support for metric kind PodList

The generated protobuf codes is already include. In this issue, it needs to add protobuf support for PodList like other existing metric type.

Resolved in https://github.com/indeedeng/k8dash/pull/202

@tianni4104 I have a question related protobuf support. How do we enable protobuf support on K8dash? Looks like the only place enabling it is the "enableProto" function: (https://github.com/indeedeng/k8dash/blob/8a75d1e6e67f551ad9141b6543156f846d62b637/client/src/utils/protoHelpers.ts#L83) but this function is not called anywhere in this repo.

@zhouxw-lang Sorry that I missed your message. We will make proto as the default method instead of json as we verified it working and can save payload body size.


Change how version string is loaded from package.json

Load package.json using require rather than a file read operation
Description
Issue #5 identified that the way this library loads its version data from package.json will
lead to either the wrong version string being put into the user-agent string or a node error
depending on which package.json file is read.
This PR remidies this issue by using require rather than a raw file read, meaning that paths
will be interpreted relative to the source file rather than from the node project root.
Motivation and Context
Issue #5, not breaking people using webpack and generally wanting to have accurate vesrion data in the user-agent string.
How Has This Been Tested?
I've tested this in a web-packed app but I also never got the error indicated in issue #5 so I'm
curious if this fixes the problems identified there.
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)

@mbish - This seems to have worked for me.

Hi @mbish .  Do you need anything else from me?  Any further testing?  Be happy to help.

Thanks very much for being willing to test this. Have you tested the update to 2eb74d9? If that works for you then I think we can move forward with this change.

Hi - I will take the latest copy and test this today.  Thank you,

I'll merge this and if @rfossella runs into problems we can do a second PR.

Hi.  So I did a clean uninstall of @duosecurity/duo_universal and then did fresh install v2.0.2.  I am now running into the same problem where the package.json file cannot be read in constants.js.
I verified this on two separate boxes after fresh install of 2.0.2  The examples package still works as it always did.
Did nothing out of the ordinary, AFAIK, just added it to my package.json and npm install.  Also as a stand-alone install command of package.  Am I missing any step(s)?

Good news.  The latest fix from package-json-fix2 seems to have worked for me.  Can we complete a new npm version?

Hi - any more updates w/this?  DUO deadline is March 31, 2024?


release sumstats for callback LEixt5ef

these were only partially released for some reason, but they all need releasing (there are about 1800 files).

Do not know why this happened but part way through publishing the studies, the process terminated. Not possible to restart so I identified those that were remaining (had not published) and manually published them.


Don't early exit concurrency search unless auto sweep mode

LGTM, do we need to handle the same thing for early stopping of max_batch_size field?

No, there are two explicit classes for sweeping model configs -- one for auto and one for manual. This was just an artifact of Perf Analyzer configuration generation being pre-computed for both auto and manual.


List all the services enabled by default

Hi, I'm not sure this is the right place to write this, tell me if this was inappropriate
Issue description
In nixos there are some services enabled by default, for example sound card. On my server I don't need sound card, so I disabled it, but since there is a lot of services in nixos I'm looking for an exhaustive list of services activated by default. If you can provide me a list, or a way to get it, I could put it here : https://nixos.org/wiki/Hardened_NixOS (or in any place more appropriate).

What do you mean by "services"?
For services.*.enable there is almost 1-to-1 mapping with systemd services. You can check them in runtime:
systemctl -a --type service

Let's check, what is enabled in Nixos by default. We will write simple configuration:
$ cat empty.nix
{
  services.sshd.enable = true;
  users.users.danbst.isNormalUser = true;
  users.users.danbst.password = "1111";
}

and run it (I'm running on server, therefore headless):
$ QEMU_NET_OPTS="hostfwd=tcp::2222-:22" $(NIXOS_CONFIG=$PWD/empty.nix nixos-rebuild build-vm; echo ./result)/bin/run-nixos-vm -display none &
$ ssh -p 2222 danbst@localhost

I see following "services" enabled "by default" in NixOS:
  UNIT                      LOAD      ACTIVE   SUB     DESCRIPTION
  alsa-store.service        loaded    active   exited  Store Sound Card State
  audit.service             loaded    active   exited  Kernel Auditing
● auditd.service            not-found inactive dead    auditd.service
  cpufreq.service           loaded    inactive dead    CPU Frequency Governor Setup
  dbus.service              loaded    active   running D-Bus System Message Bus
  dhcpcd.service            loaded    active   running DHCP Client
● display-manager.service   not-found inactive dead    display-manager.service
  emergency.service         loaded    inactive dead    Emergency Shell
  firewall.service          loaded    active   exited  Firewall
<EMAIL_ADDRESS>      loaded    active   running Getty on tty1
  kmod-static-nodes.service loaded    active   exited  Create list of required static device nodes for the current kernel
  network-local-commands.service loaded    active   exited  Extra networking commands.
  network-setup.service     loaded    active   exited  Networking Setup
  nix-daemon.service        loaded    inactive dead    Nix Daemon
  nscd.service              loaded    active   running Name Service Cache Daemon
● plymouth-quit-wait.service not-found inactive dead    plymouth-quit-wait.service
● plymouth-start.service    not-found inactive dead    plymouth-start.service
  rescue.service            loaded    inactive dead    Rescue Shell
  save-hwclock.service      loaded    inactive dead    Save Hardware Clock
  sshd.service              loaded    active   running SSH Daemon
● syslog.service            not-found inactive dead    syslog.service
  systemd-ask-password-console.service loaded    inactive dead    Dispatch Password Requests to Console
  systemd-ask-password-wall.service loaded    inactive dead    Forward Password Requests to Wall
  systemd-binfmt.service    loaded    inactive dead    Set Up Additional Binary Formats
  systemd-fsck-root.service loaded    inactive dead    File System Check on Root Device
● systemd-hwdb-update.service not-found inactive dead    systemd-hwdb-update.service
  systemd-initctl.service   loaded    inactive dead    /dev/initctl Compatibility Daemon
  systemd-journal-catalog-update.service loaded    active   exited  Rebuild Journal Catalog
  systemd-journal-flush.service loaded    active   exited  Flush Journal to Persistent Storage
  systemd-journald.service  loaded    active   running Journal Service
  systemd-logind.service    loaded    active   running Login Service
  systemd-modules-load.service loaded    active   exited  Load Kernel Modules
  systemd-random-seed.service loaded    active   exited  Load/Save Random Seed
  systemd-remount-fs.service loaded    active   exited  Remount Root and Kernel File Systems
  systemd-rfkill.service    loaded    inactive dead    Load/Save RF Kill Switch Status
  systemd-sysctl.service    loaded    active   exited  Apply Kernel Variables
● systemd-sysusers.service  not-found inactive dead    systemd-sysusers.service
  systemd-tmpfiles-clean.service loaded    inactive dead    Cleanup of Temporary Directories
  systemd-tmpfiles-setup-dev.service loaded    active   exited  Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service loaded    active   exited  Create Volatile Files and Directories
  systemd-udev-settle.service loaded    inactive dead    udev Wait for Complete Device Initialization
  systemd-udev-trigger.service loaded    active   exited  udev Coldplug all Devices
  systemd-udevd.service     loaded    active   running udev Kernel Device Manager
● systemd-update-done.service not-found inactive dead    systemd-update-done.service
  systemd-update-utmp.service loaded    active   exited  Update UTMP about System Boot/Shutdown
  systemd-user-sessions.service loaded    active   exited  Permit User Sessions
  systemd-vconsole-setup.service loaded    inactive dead    Setup Virtual Console
<EMAIL_ADDRESS>       loaded    active   running User Manager for UID 1000

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

48 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

Looks like some of those may be disabled. The mentioned alsa-store, display-manager, etc. Usually, this is matter of one import:
  imports = [
    <nixpkgs/nixos/modules/profiles/headless.nix>
  ];

(btw, as for me (17.03 69d9061908162b) the headless.nix profile doesn't disable display-manager.service, definitely a bug)

didn't know this headless thing 👍  thanks for the explanation, I'm closing this

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/huge-amount-of-default-system-services/54556/1


Escape key handlers should stop event propagation

TuSimple/naive-ui version (版本)
2.29.0
Vue version (Vue 版本)
3.2.34
Browser and its version (浏览器及其版本)
Chrome/101.0.4951.64
System and its version (系统及其版本)
MacOS (10.15.7)
Node version (Node 版本)
Reappearance link (重现链接)
https://codesandbox.io/s/admiring-lumiere-m7cq89
Reappearance steps (重现步骤)
Open the modal, then click any of the inputs, so the input popup is open, then press Escape key
Expected results (期望的结果)
The popup open by the input is closed, modal stays open
Actual results (实际的结果)
Modal closes
Remarks (补充说明)

I think we should handle the problem. However solution maybe complex.
We need to save esc event in a weak set, then check it in modal event handler.


Tailing very large .txt files doesn't work

tailing a 18mb test file containing 150.000 lines only showns ~32000 lines.

This might be related issue: https://github.com/djeedjay/DebugViewPP/issues/228#issuecomment-293224972


Fix bug in run_tests

The test_services.sh script was renamed to test_dependencies.sh as it was confusing.

:+1:

:+1:  :+1:


throw error: You are loading the ES modules build of React Router on a page that is already running the UMD build in<EMAIL_ADDRESS>+<EMAIL_ADDRESS>

<EMAIL_ADDRESS>or<EMAIL_ADDRESS>'s CDN JS
throw error
<script<EMAIL_ADDRESS>    <script<EMAIL_ADDRESS>        <script<EMAIL_ADDRESS>throw error: Uncaught Error: You are loading the ES modules build of React Router on a page that is already running the UMD build, so things won't work right.
DEMO: https://codesandbox.io/s/dazzling-lewin-cmbyo?fontsize=14
no error
<script<EMAIL_ADDRESS>    <script<EMAIL_ADDRESS>        <script<EMAIL_ADDRESS>DEMO: https://codesandbox.io/s/reverent-river-u6f6n?fontsize=14

The react-router-dom UMD builds bundle react-router, so there is no need to include both.
The reason that you don't see the error with the second one is that the Error gets removed in the production build because it behind a __DEV__ check.


Prepare release 2.5.0

What does this PR do?
This PR prepares release 2.5.0.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1822 (08ee88f) into release/2.5.0 (c098d3a) will increase coverage by 0.03%.
The diff coverage is n/a.

Additional details and impacted files
@@                Coverage Diff                @@
##           release/2.5.0    #1822      +/-   ##
=================================================
+ Coverage          83.48%   83.51%   +0.03%
=================================================
  Files                467      467
  Lines              16468    16470       +2
  Branches            2481     2482       +1
=================================================
+ Hits               13748    13754       +6
- Misses              2034     2039       +5
+ Partials             686      677       -9

see 27 files with indirect coverage changes


feat: add additional assertions to the Storable trait.

This commit adds a new method, to_bytes_checked, to the Storable trait. It includes assertions to detect if the Storable implementation of an element is buggy. This addresses the issue in #125, where a user had a mistake in their implementation of Storable, but it wasn't clear from the error that this was the case.
BTreeMap has been updated to use to_bytes_checked rather than to_bytes.

Oh wait, why did it automatically merge to the base one? Did this change recently?

I think I just did a mistake juggling the different branches. I'll fix this.

I opened #136 to replace this PR.


Strand-specific methylation-calling

Hi,
Just wanted to confirm as I couldn't find it in the documentation, does Nanopolish detect methylation on only one strand or both strands? If it's only one strand, is it just the plus strand?
Thanks!

Oh ok, thanks! I was just confused because the methylation frequency tsv file doesn't mention the strand.
I raised this issue because I was comparing methylation detection between Tombo and Nanopolish and I got a 44% similarity in sites between the two. I thought this may be because Tombo detects sites on both both the plus and minus strands, and Nanopolish might not. The Tombo output files give a methylation probability for every cytosine in the genome, so I compared these to Nanopolish to find out whether Nanopolish had overlapping sites with the minus strand in Tombo. I used BEDTools to intersect the Tombo plus strand methylation site file with the Nanopolish file, and got sites that overlapped. However, intersecting the Tombo minus strand file with the Nanopolish file gave no overlapping sites, so I thought Nanopolish wasn't detecting methylation on the minus strand.
Is there a way to get Nanopolish to output the methylation sites on minus strand separately from the sites on the plus strand? Sorry, I haven't been able to find this option for methylation-detection in Nanopolish.

This was resolved by @mike-molnar awhile back, closing this issue now


HttpObjectDecoder#isContentAlwaysEmpty does not handle upgrade responses correctly

I ran into the following when testing Undertow HTTP2 interop via upgrade. This method contains the following:
        // Correctly handle return codes of 1xx.
        //
        // See:
        //     - http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html Section 4.4
        //     - https://github.com/netty/netty/issues/222
        if (code >= 100 && code < 200) {
            // One exception: Hixie 76 websocket handshake response
            return !(code == 101 && !res.headers().contains(HttpHeaderNames.SEC_WEBSOCKET_ACCEPT));
        }

This assumes that every response that does not have SEC_WEBSOCKET_ACCEPT is a Hixie 76 response, which is obviously incorrect for HTTP2 upgrade requests. A better approach would be to check directly for Hixie 76 headers. The only way I could get h2c to work correctly was to add a fake sec-websocket-accept header to my upgrade request.

@stuartwdouglas could you link me to the code you used for testing?

https://github.com/undertow-io/undertow/commit/c44b8239e2bca6e246616b1369433e3ed85e477e
This is based on the http2 client example in the netty repo
If you remove the sec-websocket-accept header the test fails. I think a more correct approach to detect Hixie 76 would be to check for the presence of Sec-WebSocket-Key1 and Sec-WebSocket-Key2 headers.

Thanks will check!

Am 17.08.2015 um 07:38 schrieb Stuart Douglas<EMAIL_ADDRESS>undertow-io/undertow@c44b823
This is based on the http2 client example in the netty repo
If you remove the sec-websocket-accept header the test fails. I think a more correct approach to detect Hixie 76 would be to check for the presence of Sec-WebSocket-Key1 and Sec-WebSocket-Key2 headers.
—
Reply to this email directly or view it on GitHub.