Improve Celo Composer

This is an open issue for the Celo Composer Gitcoin Bounty.
The Bounty works as follows:

If you improve the user interface or create new components that you think might be useful for other developers you may be eligible for a bounty.
Meaningful and novel contributions from the community to improve or extend the project will receive a bounty ranging from 5 to 50 cUSD (or more) depending on the work.
To claim a bounty, register for the open Gitcoin bounty as a worker and link to your PR.
If you are working on something that is in heavy demand from the Celo Developer Community, be sure to get the community excited and commenting on your PR. Although PRs are welcome gitcoin bounty awards will be selected at the discretion of the Celo Foundation team.

Some starter ideas include:

improved or new documentation
improved functionality
extension of current functionality to do something novel or useful
improving readability of the project code or file structure
improved design or better support for design changes
localization of documentation into a new language

If you are unsure whether your idea is a good improvement for Celo Composer, feel free to comment below and ask for additional guidance.

@joenyzio the project type on gitcoin is currently set to Traditional, which means only one user can work on it. Please fix!

Bounty closed.


fix unicast_peer var type in readme

Description
I changed variable type in README.md. This is very small fix.

No DCO required here. Thanks for the fix

I'll add DCO later. Thanks for the merge.


[request] logging plugins(http,tcp,udp) add config field

Summary
logging plugins that should stay a per-protocol: http, tcp, udp, and can come with facilities such as a config field for the serializer and buffer.

Thanks for opening this tracking issue!
Related discussions:

#1690
#1731

Yes, I know


HBASE-22460 : Reopen regions with very high Store Ref Counts

Jira: https://issues.apache.org/jira/browse/HBASE-22460

Updated the PR with suggested changes. Please review @anoopsjohn

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 37s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:blue_heart:
prototool
0m  0s
prototool was not available.

:green_heart:
hbaseanti
0m  1s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

:blue_heart:
mvndep
1m  3s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 27s
master passed

:green_heart:
compile
3m  4s
master passed

:green_heart:
checkstyle
2m 40s
master passed

:blue_heart:
refguide
5m 38s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
4m 54s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
5m 15s
master passed

:blue_heart:
spotbugs
4m 14s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
28m  6s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 15s
Maven dependency ordering for patch

:green_heart:
mvninstall
6m 24s
the patch passed

:green_heart:
compile
3m 48s
the patch passed

:green_heart:
cc
3m 48s
the patch passed

:green_heart:
javac
3m 48s
the patch passed

:green_heart:
checkstyle
3m 14s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

:blue_heart:
refguide
7m 14s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
6m  4s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
20m  8s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
hbaseprotoc
10m 39s
the patch passed

:green_heart:
javadoc
6m  9s
the patch passed

:green_heart:
findbugs
30m 41s
the patch passed

_ Other Tests _

:green_heart:
unit
250m 39s
root in the patch passed.

:green_heart:
asflicense
5m 19s
The patch does not generate ASF License warnings.

417m 25s

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/600

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml cc hbaseprotoc prototool

uname
Linux ac7bbf7c4a4f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-600/out/precommit/personality/provided.sh

git revision
master / cb62f73406

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/2/artifact/out/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/2/artifact/out/patch-site/book.html

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/2/testReport/

Max. process+thread count
5458 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-common hbase-hadoop-compat hbase-hadoop2-compat hbase-protocol hbase-client hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 18s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:blue_heart:
prototool
0m  0s
prototool was not available.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

:blue_heart:
mvndep
0m 27s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 40s
master passed

:green_heart:
compile
3m 14s
master passed

:green_heart:
checkstyle
2m 55s
master passed

:blue_heart:
refguide
6m 10s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m  0s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
4m 56s
master passed

:blue_heart:
spotbugs
14m 53s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
26m  4s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 13s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 29s
the patch passed

:green_heart:
compile
3m 25s
the patch passed

:green_heart:
cc
3m 25s
the patch passed

:green_heart:
javac
3m 25s
the patch passed

:green_heart:
checkstyle
2m 53s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

:blue_heart:
refguide
6m 23s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m 19s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
18m  6s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
hbaseprotoc
9m 57s
the patch passed

:green_heart:
javadoc
5m 36s
the patch passed

:green_heart:
findbugs
29m 34s
the patch passed

_ Other Tests _

:broken_heart:
unit
262m 27s
root in the patch failed.

:green_heart:
asflicense
3m  3s
The patch does not generate ASF License warnings.

416m 38s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestSnapshotTemporaryDirectory

hadoop.hbase.tool.TestSecureBulkLoadHFilesSplitRecovery

hadoop.hbase.tool.TestBulkLoadHFilesSplitRecovery

Subsystem
Report/Notes

Docker
Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/600

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml cc hbaseprotoc prototool

uname
Linux<PHONE_NUMBER>f2 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-600/out/precommit/personality/provided.sh

git revision
master / cb04c6c1a6

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/4/artifact/out/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/4/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/4/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/4/testReport/

Max. process+thread count
5179 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-common hbase-hadoop-compat hbase-hadoop2-compat hbase-protocol hbase-client hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/4/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

Please review @anoopsjohn

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 30s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:blue_heart:
prototool
0m  0s
prototool was not available.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

:blue_heart:
mvndep
0m 35s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 45s
master passed

:green_heart:
compile
3m 20s
master passed

:green_heart:
checkstyle
3m 10s
master passed

:blue_heart:
refguide
6m 42s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m 20s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
5m 10s
master passed

:blue_heart:
spotbugs
3m 55s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
26m  6s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 14s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 24s
the patch passed

:green_heart:
compile
3m 16s
the patch passed

:green_heart:
cc
3m 16s
the patch passed

:green_heart:
javac
3m 16s
the patch passed

:green_heart:
checkstyle
3m  1s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

:blue_heart:
refguide
6m 11s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m  1s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
16m 59s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
hbaseprotoc
9m 12s
the patch passed

:green_heart:
javadoc
4m 58s
the patch passed

:green_heart:
findbugs
27m  5s
the patch passed

_ Other Tests _

:broken_heart:
unit
207m 59s
root in the patch failed.

:green_heart:
asflicense
3m 41s
The patch does not generate ASF License warnings.

358m 41s

Reason
Tests

Failed junit tests
hadoop.hbase.snapshot.TestExportSnapshotNoCluster

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/600

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml cc hbaseprotoc prototool

uname
Linux d61acd0cdae3 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-600/out/precommit/personality/provided.sh

git revision
master / 52f5a85bfc

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/8/artifact/out/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/8/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/8/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/8/testReport/

Max. process+thread count
5091 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-common hbase-hadoop-compat hbase-hadoop2-compat hbase-protocol hbase-client hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/8/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

Updated the PR based on latest comments. Please review @anoopsjohn

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 44s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:blue_heart:
prototool
0m  0s
prototool was not available.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

:blue_heart:
mvndep
0m 36s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 51s
master passed

:green_heart:
compile
3m 22s
master passed

:green_heart:
checkstyle
3m 11s
master passed

:blue_heart:
refguide
6m 25s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m 30s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
5m 50s
master passed

:blue_heart:
spotbugs
3m 59s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
27m 30s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 16s
Maven dependency ordering for patch

:green_heart:
mvninstall
6m  2s
the patch passed

:green_heart:
compile
3m 36s
the patch passed

:green_heart:
cc
3m 36s
the patch passed

:green_heart:
javac
3m 36s
the patch passed

:green_heart:
checkstyle
3m  8s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

:blue_heart:
refguide
6m 56s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
4m 44s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
16m 11s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
hbaseprotoc
8m 55s
the patch passed

:green_heart:
javadoc
5m 17s
the patch passed

:green_heart:
findbugs
25m 13s
the patch passed

_ Other Tests _

:broken_heart:
unit
211m  3s
root in the patch failed.

:green_heart:
asflicense
4m 58s
The patch does not generate ASF License warnings.

364m 16s

Reason
Tests

Failed junit tests
hadoop.hbase.snapshot.TestExportSnapshotNoCluster

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/9/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/600

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml cc hbaseprotoc prototool

uname
Linux cbfe87e8fc91 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-600/out/precommit/personality/provided.sh

git revision
master / ca0d9f3cd2

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/9/artifact/out/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/9/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/9/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/9/testReport/

Max. process+thread count
4660 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-common hbase-hadoop-compat hbase-hadoop2-compat hbase-protocol hbase-client hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/9/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 31s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:blue_heart:
prototool
0m  0s
prototool was not available.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

:blue_heart:
mvndep
0m 34s
Maven dependency ordering for branch

:green_heart:
mvninstall
6m  8s
master passed

:green_heart:
compile
3m 14s
master passed

:green_heart:
checkstyle
2m 58s
master passed

:blue_heart:
refguide
6m 10s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m  2s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
4m 56s
master passed

:blue_heart:
spotbugs
3m 59s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
25m 38s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 14s
Maven dependency ordering for patch

:broken_heart:
mvninstall
2m 48s
root in the patch failed.

:broken_heart:
compile
1m 53s
root in the patch failed.

:broken_heart:
cc
1m 53s
root in the patch failed.

:broken_heart:
javac
1m 53s
root in the patch failed.

:green_heart:
checkstyle
2m 58s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

:blue_heart:
refguide
6m 19s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:broken_heart:
shadedjars
3m 58s
patch has 14 errors when building our shaded downstream artifacts.

:broken_heart:
hadoopcheck
2m  5s
The patch causes 14 errors with Hadoop v2.8.5.

:broken_heart:
hadoopcheck
4m 17s
The patch causes 14 errors with Hadoop v2.9.2.

:broken_heart:
hadoopcheck
6m 30s
The patch causes 14 errors with Hadoop v3.1.2.

:broken_heart:
hbaseprotoc
0m 44s
hbase-server in the patch failed.

:broken_heart:
hbaseprotoc
2m 17s
root in the patch failed.

:green_heart:
javadoc
4m 47s
the patch passed

:broken_heart:
findbugs
0m 56s
hbase-server in the patch failed.

:broken_heart:
findbugs
8m 46s
root in the patch failed.

_ Other Tests _

:broken_heart:
unit
12m 11s
root in the patch failed.

:green_heart:
asflicense
1m 22s
The patch does not generate ASF License warnings.

124m 25s

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/600

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml cc hbaseprotoc prototool

uname
Linux fc85093077d9 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-600/out/precommit/personality/provided.sh

git revision
master / 944108c38a

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/branch-site/book.html

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-compile-root.txt

cc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-compile-root.txt

javac
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-compile-root.txt

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-site/book.html

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-shadedjars.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-javac-2.8.5.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-javac-2.9.2.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-javac-3.1.2.txt

hbaseprotoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-hbaseprotoc-hbase-server.txt

hbaseprotoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-hbaseprotoc-root.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-findbugs-hbase-server.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-findbugs-root.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/testReport/

Max. process+thread count
289 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-common hbase-hadoop-compat hbase-hadoop2-compat hbase-protocol hbase-client hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/10/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 31s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  1s
No case conflicting files found.

:blue_heart:
prototool
0m  0s
prototool was not available.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

:blue_heart:
mvndep
0m 34s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 43s
master passed

:green_heart:
compile
3m 16s
master passed

:green_heart:
checkstyle
2m 57s
master passed

:blue_heart:
refguide
6m 12s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m  2s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
4m 54s
master passed

:blue_heart:
spotbugs
3m 48s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
26m 26s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 15s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 26s
the patch passed

:green_heart:
compile
3m 19s
the patch passed

:green_heart:
cc
3m 19s
the patch passed

:green_heart:
javac
3m 19s
the patch passed

:green_heart:
checkstyle
2m 57s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

:blue_heart:
refguide
6m 21s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m  0s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
17m  4s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
hbaseprotoc
9m  7s
the patch passed

:green_heart:
javadoc
5m  8s
the patch passed

:green_heart:
findbugs
27m  7s
the patch passed

_ Other Tests _

:broken_heart:
unit
213m 19s
root in the patch failed.

:green_heart:
asflicense
3m 34s
The patch does not generate ASF License warnings.

362m 58s

Reason
Tests

Failed junit tests
hadoop.hbase.snapshot.TestExportSnapshotNoCluster

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/11/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/600

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml cc hbaseprotoc prototool

uname
Linux d8739debc6af 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-600/out/precommit/personality/provided.sh

git revision
master / 52176184df

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/11/artifact/out/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/11/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/11/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/11/testReport/

Max. process+thread count
4953 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-common hbase-hadoop-compat hbase-hadoop2-compat hbase-protocol hbase-client hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/11/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

@apurtell @anoopsjohn The status on this so far:

Based on suggestion from Anoop, I will create a follow up Jira for turning this feature on/off using ConfigurationObserver(without HM restart) once this is ready for commit.
Addressed recent review comments

Since release preparation for 1.5 is on the way, I was wondering if this should go to 1.5. Since procedures are not present on branch-1, backport work is required. Just wanted to know how quickly this should land to 1.5 if it is supposed to go to 1.5.
Thanks

@apurtell Please review as per your convenience

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 29s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:blue_heart:
prototool
0m  0s
prototool was not available.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

:blue_heart:
mvndep
1m  2s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 40s
master passed

:green_heart:
compile
3m 18s
master passed

:green_heart:
checkstyle
3m  6s
master passed

:blue_heart:
refguide
6m 19s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m  0s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
4m 56s
master passed

:blue_heart:
spotbugs
3m 55s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
25m 43s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 14s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 25s
the patch passed

:green_heart:
compile
3m 15s
the patch passed

:green_heart:
cc
3m 15s
the patch passed

:green_heart:
javac
3m 15s
the patch passed

:green_heart:
checkstyle
3m  3s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

:blue_heart:
refguide
6m 13s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

:green_heart:
shadedjars
5m  1s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
18m 16s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
hbaseprotoc
9m 45s
the patch passed

:green_heart:
javadoc
4m 57s
the patch passed

:green_heart:
findbugs
27m  6s
the patch passed

_ Other Tests _

:broken_heart:
unit
175m  4s
root in the patch failed.

:green_heart:
asflicense
3m  6s
The patch does not generate ASF License warnings.

326m 19s

Reason
Tests

Failed junit tests
hadoop.hbase.master.TestClusterRestartFailoverSplitWithoutZk

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/12/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/600

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml cc hbaseprotoc prototool

uname
Linux 2c13845cae63 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-600/out/precommit/personality/provided.sh

git revision
master / 2ad62b0162

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/12/artifact/out/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/12/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/12/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/12/testReport/

Max. process+thread count
4622 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-common hbase-hadoop-compat hbase-hadoop2-compat hbase-protocol hbase-client hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-600/12/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.


Do not run staticcheck on generated protobufs

Fixes #314
The current staticcheck GitHub action doesn't support directory exclusions. I've implemented a matrix directory approach to fix issue #314. However, I suggest we move away from the staticcheck action entirely and create a new golang-lint CI action (taking inspiration from collector repo ci setup) instead. If that sounds good, I will create a separate PR(s) for the proposed change. Let me know what you think.

However, I suggest we move away from the staticcheck action entirely and create a new golang-lint CI action (taking inspiration from collector repo ci setup) instead. If that sounds good, I will create a separate PR(s) for the proposed change. Let me know what you think.

Sounds good to me. In the meantime I will merge this PR to unblock the other PRs.


Error: Cannot find module 'vue' on Heroku;

Hello there.
I've created a new app using starter template, it's almost empty, works fine on local machine and gives me this error on heroku:

I have another nuxt app there, with older nuxt version and it works as intended, so I don't know what  it could be.
Adding package.json, maybe it helps.
 "name": "<>",
  "version": "1.0.0",
  "description": "<>",
  "author": "<>",
  "private": true,
  "dependencies": {
    "css-loader": "^0.27.3",
    "firebase": "^3.7.3",
    "nuxt": "latest",
    "vue": "^2.2.6"
  },
  "scripts": {
    "dev": "nuxt",
    "build": "nuxt build",
    "start": "nuxt start",
    "generate": "nuxt generate",
    "lint": "",
    "precommit": "npm run lint",
    "heroku-postbuild": "npm run build"
  },
  "devDependencies": {
    "node-sass": "^4.5.0",
    "sass-loader": "^6.0.2",
    "webpack": "^2.2.1"
  }

I'm seeing the same issue here. It worked fine with v0.9.x but since updating to v0.10.0 I've been getting this as well.

I've deployed empty application to heroku. The only change I did was adding  "heroku-postbuild": "npm run build" line to package.json and gitignoring .idea folder.
ENV vars are ofcourse set as intended:

Repo which I deployed to double-check is here.
Sadly, this error persirst even with blank app. :( Thats why I suspect this might be an issue with nuxt or its dependencies itself, though I don't have any ideas how could I help fixing it without diving into nuxt core :(.
Hope this helps.

I can confirm 0.10.x can't be deployed to heroku with empty nuxt/starter template .
I tried it today , and got same error .
console have show some dependence warning/error , but I lost that information .

👋 Hey all, I believe this is actually a duplicate of #462. The solution in that thread worked for me on Heroku. Best of luck!

@paulstraw Yup, that worked for me too, thanks.
Hope it gets fixed by default in future releases.


Linter not strict enough - for example indentation

Initial discussion here https://github.com/EddieJaoudeCommunity/EddieBot/pull/181#discussion_r475092290

Let's have one for if statements as well.
https://palantir.github.io/tslint/rules/curly/
docs for semicolon:
https://palantir.github.io/tslint/rules/semicolon/

TSLint is deprecated see https://github.com/palantir/tslint/issues/4534, They are migrating to ESLint and i think we should move to ESLint to 😁

Yes good point @alrifay , we should be using eslint now, even for typescript


Peerswap web on Umbrel App Store?

Hi Vlad,
thank you for your efforts and for providing the Peerswap Web.
I would like to use your solution on an Umbrel Home but I am not familiar with docker installation and I don't want to break something.
I just read in this article PeerSwap on an Umbrel Home that you are working on an Umbrel App store app for theePeerSwap Web UI. Could you please give us an idea when this might be ready.
Thanks a lot,
Thomas

Hello Thomas. I submitted PeerSwap for Umbrel on January 9, some 1.5 months ago. They still did not review it. I don't know how to push this process, I offered my help there and in Discord. Maybe you can leave a comment to ask this question? Meanwhile, I use PS on my Umbrel with Elements Core installed via App Store and with PeerSwap and PeerSwap web both installed manually with Go.

Thank you, Vlad.
I posted a comment and asked @smolgrrr about their progress.
Hope your solution will make it soon in the official Umbrel App store since I am not familiar installing manually.


Add QML templates module

Adds a "models" (now called "template") module for providing templates for easy construction of qml models including documentation.
This is just to get things going in this direction. Would be nice to add more such templates in response to #133. @mariaschuld , you probably have the best overview of existing architectures. Would be great if you could contribute.

I still need to polish this a bit more, but we now basically have a working very general Interferometer implementation in PL and QML models for the CV neural network and the circuit centric classifier architecture.

One thing we should think about again, and my hope is that @mariaschuld has an opinion on this is the name of this sub-module: Wile "model" looks nice if one calls the code from here in a qnode by means of something like qml.model.CVNeuralNet(...), it is questionable whether we should not reserve the name "model" for a circuit plus parameters. We will certainly at some point want to implement a way for users to save and load readily trained QML models.
Alternative names for this module could be 'template' or 'circuit' (but I am not too happy with 'circuit' either).

Sorry for coming into the discussion only now. To me, "model" makes sense to a full algorithm that fulfills some ML task. The quantum submodule is just the quantum node of a model, if the model is a hybrid computation...So if I understand it correctly, to have a model library where i.e. a CVNN can be called from is perfect!

Will do PR review tomorrow morning.

I like the change to the name "template".
"Model" implies not only a circuit architecture, but also a trained set of weights (which distinguish the model from other models which might have the same architecture but different weights).
With "template" it is more clear that while the circuit architecture is given, the parameters should still be "filled-in" by the user

One other thing: The name "Circuit Centric Classifier" obviously links the template directly to the paper name. However, that name might be too generic to be a good template name (since one can imagine endless permutations which use quantum circuits to build a classifier).
I wonder if we can we can come up with something that is more descriptive of the type of circuit that is actually used in this template?

@cgogolin something that I've just noticed/been thinking about. While it's nice to have the Clements decomposition as an option for the interferometer, it feels a bit out of place.

If thought of as a operation/decomposition, it goes against the PennyLane 'design', where PennyLane operations act as placeholders to be interpreted by the plugins. See QubitUnitary, etc, where the decomposition is left to the plugin.

If instead thought of as a template or an ansatz, it also doesn't quite fit in, since it cannot be parameterized (as you note in the docstring).

I'm also a bit hesitant to include the same Clements decomposition code separately across both PennyLane and Strawberry Fields, as it increases the maintenance load.
Perhaps the Clements decomposition is something we could revisit in another issue or PR? If used in both Strawberry Fields and PennyLane, it might even make sense to 'spin it out' into it's own Python package and make it a dependent in both.

I'm not sure I understand why it cannot be parametrized. Surely your interferometer takes angles or U? Isn't that what we mean by parametrised?
I see your design principle concerns though. But then we would need a gate container to make SF implement it instead, right?


Issue with PHP_BINARY

I'm running PHP-FPM on my server, so when I try and use this commandbus library with the background async process it never actually runs anything because the PHP_BINARY is set to "php-fpm" and php doesn't run commands on that. Any ideas?

PR for this issue is #19

Why not to set backgroundHandlerBinary manually? This should solve your problem.

@trntv
That shouldn't be a solution since this should do its best to determine what php binary to use dynamically.
Also, since I'm going between different environments, prod, staging, ci, dev.. the binary might change. Also my co workers are probably using a different environment than I am so hard coding the variable should not be a solution.
The PR I submitted should take care of all these problems.

@trntv any updates on this?

To be honest, i don't like any kind of programming "magic" this one is a kind of it. I still think that if you can provide binary path by configuration you should do it. You can extend this middleware manually, run your magic when initializing command bus etc.


⚠ Guya.moe Proxied has degraded performance

In 43c7242, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 13173 ms

Resolved: Guya.moe Proxied performance has improved in d673d0f after 57 minutes.


<EMAIL_ADDRESS>

For prosperity, we're forcing this through despite the CI failures, as they're unrelated to the 0.22.0 -> 0.22.1 diff (https://github.com/bazelbuild/rules_python/compare/0.22.0...0.22.1).


fix typo and grammar in README.md

add definition of CMS to clarify meaning for readers

Awesome! @JamesBie 👍


Filters on video

Hi, is it possible to apply image filters? for example grayscale, image rotation etc... Have you already tried it? I need to apply filter which will be in video preview and also in recorded video. What do you think about performance? Or should I use metal for this feature?

No. It is out-of-scope from this framework.
I think you need to do extra work on your side.

All filter operation should be performed inside GPU world. Use CoreImage, etc.
Render CVPixelBuffer into CIImage
Apply CIFilter into CIImage
Create output CVPixelBuffer with applied CIImage
Create new CMSampleBuffer using CVPixelBuffer with proper orientation info
Enqueue CMSampleBuffer into export session and/or display session
For Image quality, either YUV444 or RGB444 format run better than yuv422/yuv420 format.

Also you need to separate pipeline for export and display.

Use most of GPU performace to process real time processing for export
To save GPU memory, reduce display image resolution into half or quarter size
Display pipeline must support instant frame drop - you need to track display time stamp of CMSampleBuffer continuously

thank you for hint


Integration Tests Covering the Snapshot and CDC iterators

@hariso @maha-hajja pls review the PR and share the observations


removing test for symbolic values cache running on different devices

removes unnecessary devices in tests

follow up for comment https://github.com/Lightning-AI/lightning-thunder/pull/1260#discussion_r1792608435

tagging @t-vi for a merge stamp.


Using codenarc.xml to define rules

Is it possible to leverage my existing codenarc.xml file to define the rules being used?
Since it seems likely there are other solutions, my desire is to have both:

VS-code highlighting of lint errors
lint validation in my gradle+groovy project build

I'm currently using the ru.vyarus.quality plugin, but could definitely swap that out if there's something that can work with npm-groovy-lint and use the same rule configuration.

If you define a npm-groovy-lint config file ( .groovylintrc.js ) at the root folder of your repo folder, both npm-groovy-lint and VsCode Groovy Lint will use it ( npm-groovy-lint is behind VsCode Groovy Lint)
Once your .groovylintrc.js file is defined :

VsCode Groovy Lint will automatically detect it , so no additional config
Add npm-groovy-lint command in your gradle build instructions ( requires npm install npm-groovy-lint -g before

( and maybe someday i'll create a script to convert codenarc ruleset file into .groovylintrc.js 😄 )

Thanks! I'll try that.

I'm not a gradle expert, but as far as i know, to use npm-groovy-lint you need to call it via command line: there is no gradle plugin using it ( but there is a codenarc one, who reads codenarc rulesets )
If you don't find an ok solution, i'll try to manage VsCode Groovy Lint to use ruleset format but, but directly calling codenarc with code built using VsCode GroovyLint may trigger issues : for example, npm-groovy-lint has an extended way to ignore rules , that code CodeNarc does not understand
My best advice would be to succeed to call npm-groovy-lint via Gradle, then you'll be ok :)
Please let me know how you solved your case :)


Code page seems to be broken

I wrote a simple cpp code 'program.cpp', encoding in utf8, for only printing a chinese string:
#include<iostream>
int main()
{
    std::cout << "哈哈哈哈哈哈" << std::endl;
    return 0;
}

But it actually printed a wrong string:
> g++ .\program.cpp
>  .\a.exe
鍝堝搱鍝堝搱鍝堝搱

cmd & powershell
The current code page of cmd or powerhsell is 936-gbk. But I can use chcp 65001 to solve this problem:
>a.exe
鍝堝搱鍝堝搱鍝堝搱

>type program.cpp
#include<iostream>
int main()
{
    std::cout << "鍝堝搱鍝堝搱鍝堝搱" << std::endl;
    return 0;
}

Active code page: 65001

>a.exe
哈哈哈哈哈哈

>type program.cpp
#include<iostream>
int main()
{
    std::cout << "哈哈哈哈哈哈" << std::endl;
    return 0;
}

pwsh
The current code page is 65001-utf8. I cannot get correct chinese strings printed, and chcp 65001 doesn't work.
> .\a.exe
鍝堝搱鍝堝搱鍝堝搱
> cat .\program.cpp
#include<iostream>
int main()
{
    std::cout << "哈哈哈哈哈哈" << std::endl;
    return 0;
}

Active code page: 65001
> .\a.exe
鍝堝搱鍝堝搱鍝堝搱
> cat .\program.cpp
#include<iostream>
int main()
{
    std::cout << "哈哈哈哈哈哈" << std::endl;
    return 0;
}

Environment data
zh-cn win10.
> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Please test with latest PowerShell 7.1 Preview build.

7.1.0-preview6, this problem still exists. It behaves the same as what 7.0.3 behaves.

How do you change active code page? If you in the same session you should use [Console]::OutputEncoding = <nnn>

[console]::outputencoding = [system.text.encoding]::utf8 works.
Hmmm, I'm confused.
Before changing code page, $outputencoding shows the encoding is utf8 and [console]::outputencoding shows the encoding is gb2312. What's the differences between $outputencoding and [console]::outputencoding?
The 'current code page' in properties shows the encoding is utf8, where does it come from?
If input chcp, it prints 'Active code page: 936', where does this result come from?
chcp 65001 doesn't change the [console]::outputencoding or $outputencoding, but in powershell it surely changes something to make the output to be decoded correctly. Why it fails in pwsh?

(If your application requires a specific codepage to be active, it should set it itself. It is almost always incorrect to rely on the global state of the console, because it will rarely be what you want.)

@YF1999 You can see https://stackoverflow.com/questions/40098771/changing-powershells-default-output-encoding-to-utf-8 for additional information.

(If your application requires a specific codepage to be active, it should set it itself. It is almost always incorrect to rely on the global state of the console, because it will rarely be what you want.)

I don't understand.
If pwsh's encoding is not the same as my program, the output from my program can be decoded correctly?
I wrote a c# program to output '哈哈哈哈哈哈', succeeded if [console]::outputencoding is gb2312, utf8 and utf7, but if is ascii it prints '??????'. If this c# program will automatically set the codepage itself, why it fails if global codepage is ascii?
There is not this problem for python and node programs, but electron programs only succeed if global codepage is utf8.

If this c# program will automatically set the codepage itself, why it fails if global codepage is ascii?

Your program does not set a code page.
https://stackoverflow.com/questions/45575863/how-to-print-utf-8-strings-to-stdcout-on-windows


Update documention with valid InputEventType in input JSON

Update documention with valid InputEventType in input JSON

Update compatability to Tomcat8,
Remove REMReM Publish Common from Components.
Remove usage of Common also.
}, in 400 status code example.
Is 404 still needed


Update rmodels.c; free fileData for LoadModelAnimationsGLTF

fileData wasn't freed for LoadModelAnimationsGLTF causing a memory leak. Added UnloadFileData line, freeing it.
With a test of just loading and unloading animations from a glb file; this change clears up the following memory leak reported via valgrind.
==7704==
==7704== HEAP SUMMARY:
==7704==     in use at exit: 62,960 bytes in 1 blocks
==7704==   total heap usage: 193 allocs, 192 frees, 388,008 bytes allocated
==7704==
==7704== 62,960 bytes in 1 blocks are definitely lost in loss record 1 of 1
==7704==    at 0x4842794: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==7704==    by 0x493EA95: LoadFileData (in /raylib/libraylib.so.450)
==7704==    by 0x48E0A1B: LoadModelAnimations (in /raylib/libraylib.so.450)
==7704==    by 0x10967E: main (animtest.c:22)
==7704==
==7704== LEAK SUMMARY:
==7704==    definitely lost: 62,960 bytes in 1 blocks
==7704==    indirectly lost: 0 bytes in 0 blocks
==7704==      possibly lost: 0 bytes in 0 blocks
==7704==    still reachable: 0 bytes in 0 blocks
==7704==         suppressed: 0 bytes in 0 blocks
==7704==
==7704== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

becomes
==7912== HEAP SUMMARY:
==7912==     in use at exit: 0 bytes in 0 blocks
==7912==   total heap usage: 193 allocs, 193 frees, 388,008 bytes allocated
==7912==
==7912== All heap blocks were freed -- no leaks are possible
==7912==
==7912== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

I'm unsure if there's anything else to be aware of in the block of code preceding the change; please let me know if there is.
Thanks!

@crynux Wow! Good catch! Thanks for the fix!


clarify the relation between matrix normal distribution and multivariate_normal

A follow-up to https://github.com/scipy/scipy/pull/5296: it'd make sense to clearly document the behavior w.r.t. singular matrices, also the relation to the multivariate normal.

Fixed by https://github.com/scipy/scipy/pull/5517, so closing.


DVCS config field.

I've wanted gx to have closer integration with git (and others) for quite a while. I think the best way to do this would be to have a "DVCS" field in the config that contains some fields like:
"DVCS": {
    "type": "git",
    "path": "github.com/whyrusleeping/gx"
}

More fields I can imagine would involve automatic hooks, like a post-publish hook that automatically commits something like "gx publish version 1.4.5".

can it be part of the path? sideband things like this is what causes pain and causes https://github.com/multiformats to exist. Can this be a prefix on the path? either with /git/ or git/ ?

eh, it could be. but its going to be more annoying. Everything that uses it will have to split it out, and that likely means lots of shell tools will have to learn how to do that.

fair enough


Invalid link in docs

On the introduction page, at the bottom, the link to documentation gives a '404 Page Not Found'.

oops, wrong repo

sure, I'll do my best.
Is there a way to move the issues to the correct repo?

https://github.com/keshavbiswa/confuscript-site


Spark settings for a namespace via REST/CLI

Does Mist support providing spark config and other settings per namespace via REST Http Request or CLI ? From the documentation, we can provides settings for an namespace in mist config file. If a namespace setting doesn't exist in config file then default context settings are used. However, I want to dynamically provide these configurations via REST/CLI. Is it possible?

Hey @goelrajat
Yes, that's very useful feature and we have it in a roadmap.
We have a settings page in our UI and the next minor release will have a feature of reloadable config file.
So, the next final minor step is be to expose this through settings API.
Would be happy to collaborate on this issue.

Thanks. Will look forward to reloadable config feature.


Add detection of generated IntelliJ files

Classify the .idea/ files generated by the IntelliJ IDEA family of IDEs (IDEA, PhpStorm, RubyMine, GoLand, etc) as generated.

Hi i m owner developer

I'm not entirely sure we should be marking everything inside an .idea directory as generated.

Isn't it the other way around? The files are definitely generated (the IDE creates them automatically when I open a folder), but not necessarily vendored (you might check in some of them)? Or am I mixing up the definitions?

Isn't it the other way around? The files are definitely generated (the IDE creates them automatically when I open a folder), but not necessarily vendored (you might check in some of them)? Or am I mixing up the definitions?

No, that's correct. The key difference is that generated files don't show up in diffs on GitHub, whereas vendored/documentation files do. However, sometimes changes to machine-generated files need to be visible to reviewers (see #4348 for an example). Hence why I asked if it'd be more appropriate if we mark these files as vendored (and only the high-churn ones as generated). I should also mention I have zero knowledge of JetBrains IDEs, hence why I'm trusting your knowledge more than mine.

generated files don't show up in diffs on GitHub,

They do, but they're collapsed by default, yes?
Re the yarn reference: yes, that's valid, but all the .idea files hold is IDE/project settings. For instance, my workspace.xml has personal stuff like my recent commit messages, VCS settings, spellcheck settings, etc.
The files they say you can commit (real examples from one of my JS projects):

myproject.iml:

<module type="WEB_MODULE" version="4">
  <component name="NewModuleRootManager">
    <content url="file://$MODULE_DIR$" />
    <orderEntry type="inheritedJdk" />
    <orderEntry type="sourceFolder" forTests="false" />
  </component>
</module>

vcs.xml:

<project version="4">
  <component name="VcsDirectoryMappings">
    <mapping directory="$PROJECT_DIR$" vcs="Git" />
  </component>
</project>

misc.xml:

<project version="4">
  <component name="JavaScriptSettings">
    <option name="languageLevel" value="ES6" />
  </component>
</project>

Nice-to-haves if you want to share them, maybe, but none of these files really matter—once you open a folder in the IDE, it regenerates the whole .idea/ folder if it doesn't exist. (In fact, I haven't seen a project where they were consciously shared, though I have seen accidental check-ins from newbie devs, along with .DS_Store😅.)
There don't seem to be any malicious opportunities from hidden diffs, except messing with your teammates, and they can easily change the setting back in their IDE.


Concat does not dispatch

http://ramdajs.com/0.19.1/docs/#concat

Dispatches to the concat method of the second argument, if present.

let R = require("ramda");

class Buffer {
  concat() {
    console.log("called!");
  }
}

R.concat([1], new Buffer()); // no luck

docs are wrong. concat is treated as infix, so first arg dispatches

Ah, another point for adding controllable multidispatch https://github.com/ramda/ramda/issues/1634
It's really important to dispatch on second argument here.

I see. Duplicate of https://github.com/ramda/ramda/issues/1604


Issue 14963: XREF and XREF_PACKED_NAMED should use relative, not absolute, URLs

Fixes: https://issues.dlang.org/show_bug.cgi?id=14963
Using absolute URLs break the doc tester, local dlang.org installations, as well as cross-module links in phobos-prerelease, as it forces everything to point to http://dlang.org/phobos/.
This reverts the generated links back to relative URLs.

This breaks links from outside the Phobos docs. E.g., the link to std.algorithm.mutation.copy on /arrays.html
Defining XREF differently in std.doc/doc.ddoc may be a way out.
/library/ has a deep directory structure, but doesn't seem affected by this (I didn't check thoroughly, though). I guess they have their own XREF already.

Yeah there are several different definitions of XREF. I guess the correct solution would be to override(?) it in std.doc or doc.ddoc.

As far as I see, /phobos-prerelease/ pages are the only ones that shouldn't link to /phobos/.
So I think a good solution would be to link to /phobos/ by default, and use links to the current directory on Phobos pages (release and prerelease).
That is, in dlang.org.ddoc define XREF with $(A $(ROOT_DIR)phobos/std_...), and then override it in std.ddoc with $(A std_...).

Fixed and rebased. Please review. Thanks!

LGTM

Same here ddoc builder though spews error 500 so it's hard to asses the results. @CyberShadow ?

sigh fixed

@CyberShadow  are you sure? I got another one at:
http://dtest.thecybershadow.net/artifact/website-4918c9d6ef9ceb055decd05eec6fc38c8fd26229-8d87c04a1173413135bdd41c727037e9/web/library/std/algorithm/iteration/each.html

Thanks, gave it a harder kick. Maybe it'll stick this time :)

Seems to work now.
Checked a few links in phobos/, phobos-prerelease/, array.html, seems to point to the right places now.  Reviewers?

Reviewers?

Still looks good to me.

ping @MartinNowak @andralex @jmdavis @CyberShadow
This has been stagnating, and in the meantime links on dlang.org are leading to the wrong places. Can we move forward with this please?

Looking at the diff, some links in DDox are getting broken, e.g. in http://dtest.thecybershadow.net/artifact/website-6f1c238c51e767f03f0887a0aab3d2f252fba173-8dfaecbab23ee25ffaf19d15442aee16/web/library-prerelease/std/algorithm/comparison/among.html the link to find now leads to a 404. Not sure what to do about this though, does DDox override some macros to fix links to use its URL structure or something?

Hmm no idea.  The link macros are a mess... they are defined somewhere and then variously overridden in other places, and it's not obvious which file(s) use which override.

some links in DDox are getting broken

As far as I can tell, the problem is that XREF_PACK_NAMED isn't being overridden in std-ddox.ddoc. It's also missing XREF2. They currently generate links to /phobos/ which too is wrong, of course (but better than 404 links).
ddox It seems to recognize the dotted names and generate links for them. I don't know how to make named links that way.

Other links from /library/ to the rest of dlang.org are broken, too. E.g. the link "Introduction to std.datetime" on http://dlang.org/library/std/datetime.html.
As far as I can tell, ddox doesn't provide a straight-forward way to link from the generated pages to other parts of the site. And I can't think of a non-straight-forward one.
As a band-aid, I suggest to add overrides like the following to std-ddox.ddoc:
XREF2 = $3 (std.$1.$2)
XREF_PACK_NAMED = $4 (std.$1.$2.$3)

This way, the short names are not links, but the fully qualified names in the parentheses are recognized by ddox and linked properly. It's ugly, but at least we get proper, relative links, and all the information is there.
We should find a way to make nicer XREF links (and fix the other broken ones). But I think that shouldn't block this PR. We're better of with ugly links that point to the right pages than the other way around.

As a band-aid, I suggest to add overrides like the following to std-ddox.ddoc:

That sound like the way to go. @quickfur ?

@quickfur Ping

@quickfur ?

It's been a good while, could someone take this over? Thanks.

Sorry, been too busy to get back to this. Yes, please let someone else take it over.


Current GraalVM version not supported

Graal has changed its versioning and it's causing problems for the plugin.
[ERROR] Failed to execute goal com.gluonhq:gluonfx-maven-plugin:1.0.18:compile (default-cli) on project fxproject: Error: Current GraalVM version (17.0.7) not supported.
[ERROR] Please upgrade to 22.1 or higher

Fixed with https://github.com/gluonhq/substrate/pull/1222
It can be tested with plugin 1.0.19-SNAPSHOT using <pluginRepository/> with url http://oss.sonatype.org/content/repositories/snapshots/

This brings up the question again whether it is actually allowed/reccommended to use the latest GraalVM with the Gluon plugin. The documentation still states:
[...] to create native-images for your Gluon application, you will need the latest version of the Gluon built version of GraalVM. which is still GraalVM CE Gluon <IP_ADDRESS>-Final from 2022-06-08.
So, does Gluon recommend and support the latest official GraalVM version and is it now fully compatible with JavaFX and the tooling or not?

Indeed, to use the GluonFX plugins, the GluonFX docs recommend the Gluon's GraalVM build https://github.com/gluonhq/graal/releases/tag/gluon-<IP_ADDRESS>-Final
which is mostly needed for the mobile targets, while on desktop, the official GraalVM build could be used as well.
However, there's no guarantee that any new change in the official build is immediately supported by the GluonFX plugins.

Hi @jperedadnr is the GRAALVM for linux working for the architecture aarch64?
thank you


Add dynamo-restore-from-s3 script to bin

Since dynamo-restore-from-s3 is missing in the bin section of package.json, dynamo-restore-from-s3 command is not found on global npm package installation. Adding it fixes the issue.

Duplicate of #70


Implement req.clone()

Implements web.Request.clone()

Current coverage is 98.78% (diff: 100%)

Merging #1361 into master will increase coverage by <.01%

@@             master      #1361   diff @@
==========================================
  Files            29         29
  Lines          6750       6762    +12
  Methods           0          0
  Messages          0          0
  Branches       1118       1123     +5
==========================================
+ Hits           6668       6680    +12
  Misses           38         38
  Partials         44         44

Powered by Codecov. Last update 7e2b762...e12a743


hue-hive.rpm is not built

While building hue - rmp's for all components are build, except hive. There is no hue-hive-4.5.0-1.el7.x86_64.rpm at the end. What can cause it?
Any help is appreciated!

Because it was absent in my hue.spec)


Remove obsolete limitations

It's not true anymore that one user can run just one shell at the time. It's possible now to run Bash and PowerShell at the same time in different tabs.
Connect-AzAccount (its alias Connect-AzureRmAccount) and Connect-AzureAD work now without a problem. Authentication changed to the devicelogin-based.

@alexandair : Thanks for your contribution! The author, @maertendMSFT, has been notified to review your proposed change.

Merging per email from @arob98


Add an option to let GestureDetector/InkWell trigger onTap/onTapUp when doubleclick

Use case
Currently, GestureDetector/InkWell:

Does not trigger onTap/onTapUp on double tap, only onDoubleTap/onTapDown.
If the onDoubleTap event is enabled, onTap/onTapUp is triggered with a delay(300ms?) on single tap, #50458.

This design may not be a big problem on mobile platforms, since double taps are not used very often.
But on desktop, it's everywhere and the user experience is poor due to the onTap latency.
onTapDown is not delayed, but it cannot replace onTap/onTapUp.
Proposal
It's better to add a global option to:

Trigger onTap/onTapUp without a delay on single tap no matter the onDoubleTap is enabled or not.
Make GestureDetector/InkWell also trigger onTap/onTap(without a delay) on double tap.Take Microsoft's WPF framework as an example, on double tap, it triggers MouseLeftButtonDown/MouseLeftButtonUp twice and MouseDoubleClick once.

This issue affects all widgets using GestureDetector/InkWell, all of them feel lag on desktop if onDoubleTap is enabled.
Is anybody working on this?

Hi @ngugcx, thank you for reporting this issue. However, the behavior you are describing is expected when using a TapGestureRecognizer and a DoubleTapGestureRecognizer, which GestureDetector does if given both callbacks.
The delay described is necessary when deciding which GestureRecognizer is to win in the GestureArena. kDoubleTapTimeout is the time that the second tap should come before so the action can be considered a double tap. On native desktop (I'm on macOS), if the amount of time between the first tap and the second tap is too long then the double tap action is not initiated. An example would be if I tap down on a word in a text field and wait 1 second to release the tap and tap down again, then a double tap is not registered.
To achieve tap and double tap behaviors without a delay, you might want to use SerialTapGestureRecognizer. Which does not delay onTap/onTapUp because it declares victory in the GestureArena as soon as a tap is detected. The count given in SerialTapDownDetails and SerialTapUpDetails can then be used to determine what to do on a single tap/double tap.
There is one caveat, being that SerialTapGestureRecognizer is not available through GestureDetector, and you would have to use it by passing it to RawGestureDetector. If SerialTapGestureRecognizer

Thanks! @Renzo-Olivares . I've not tried SerialTapGestureRecognizer, but after reading the doc, I think it matches my use case.
The problem is that InkWell/GestureDetector are regarded as the higher level way to handle mouse events. Lots of controls including the offical ones (tab, list ...) use InkWell/GestureDetector.
I know why the delay exists in InkWell/GestureDetector. But I don't understand why they are designed like that, are there many cases where only double-tap is used?

For the desktop, the mouse is very important. If Flutter is perfunctory with the mouse, the user experience of the desktop will be out of the question.

Hi @Renzo-Olivares and @ngugcx
Ngugcx is correct. Gesture detector and Inkwell widgets should absolutely implement some sort of bool to override ontap() delay when ondoubletap() is implemented, especially on desktop. If onTap is benign (doesn't perform a critical action) as it is in most desktop-based systems, there is no reason it can't be implemented sequentially with onDoubleTap.
On desktop, the simple act of clicking once on an object to obtain selection focus and double clicking to execute has been around as long as graphical OSs have. It needs to be fixed without a complex implementation on our part to bring it inline with literally  'everything else in the world'. It makes all desktop apps sluggish and unresponsive.

I'd also prefer a more standard solution to this problem than fiddling around with the SerialTapGestureRecognizer. I mean, look at how much more verbose and janky this code is:
RawGestureDetector(
          gestures: <Type, GestureRecognizerFactory>{
            SerialTapGestureRecognizer: GestureRecognizerFactoryWithHandlers<SerialTapGestureRecognizer>(
              () => SerialTapGestureRecognizer(),
              (SerialTapGestureRecognizer instance) {
                instance
                  ..onSerialTapDown = (SerialTapDownDetails details) {
                    print(details.count);
                    if (details.count == 1) {
                      widget.onTap();
                    } else if (details.count == 2) {
                      widget.onDoubleTap();
                    }
                  };
              },
            )
          },
      child: child
}

compared to the relative niceness of the standard GestureRecognizer:
 GestureDetector(
    onTap: widget.onTap;
    onDoubleTap: widget.onDoubeTap,
    child:  child,
)

And like ngugcx says, all the documentation focuses on the easier (but worse) solutions.
Some kind of overeride in gesture detector would be nice. Or a way to otherwise specify what kind of algorithm to use. Because on desktop, the standard click/double click interaction feels painfully laggy.

@Renzo-Olivares , almost one year passed, any progress on this issue and the new design? thanks.

In the desktop environment, there is no good cross-platform GUI framework. Flutter desktop is very promising, but it's a pity that Google doesn't take it seriously.

Apologies for the lack of updates as I have not been actively working on this issue. I have bumped the priority on this issue and will be giving it another look. Thanks for the patience.

This issue is affecting a production Google app using desktop web - see internal bug b/322887506 for context. The existing behavior does not break the functionality seeing as it is still possible to do everything, however it creates a perception of jank and makes the user experience feel very wrong.
While SerialTapGestureRecognizer works for simpler cases, it seems like there is a usability issue here. There should be an obvious way to achieve this functionality seeing as it's very common on desktop web and desktop native, and it should be possible even when it's not the same widget recognizing the single and double clicks. The widget tree could have a nested single click recognizer that is in a completely different file etc.
Here is some minimal repro code in case it's handy for anyone:

Repro code for Dartpad
import 'package:flutter/material.dart';

const Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark().copyWith(
        scaffoldBackgroundColor: darkBlue,
      ),
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: TappingDemo(),
        ),
      ),
    );
  }
}

class TappingDemo extends StatefulWidget {
  @override
  State<TappingDemo> createState() => _TappingDemoState();
}

class _TappingDemoState extends State<TappingDemo> {
  String text = "";

  @override
  Widget build(BuildContext context) {
    return Column(children: [
      Text('Sequence of single and double taps: $text'),
      GestureDetector(
        onDoubleTap: () {
          setState(() {
            text = text + 'D';
          });
        },
        child: ElevatedButton(
            child: Text('Press me'),
            onPressed: () {
              setState(() {
                text = text + 'S';
              });
            }),
      ),
    ]);
  }
}

Inlining a slightly modified (reduced) version of the duplicate issue I opened at #113906...
I'd like a way to disable the delay, implying both events may fire. I've developed a couple small apps for Flutter Desktop and in each app, where I've wanted tap and double tap on the same widget, I've not wanted the delay imposed.
Issue #22950 discusses adjusting kDoubleTapTimeout to reduce the delay, but that's not an appropriate solution as it simply makes double clicks harder to achieve and still will have a noticeable delay if configured so that double click is usable.
In one instance I was able to use SerialTapGestureRecognizer  (https://discord.com/channels/608014603317936148/1030649689802035251/1031017424935460926), but that isn't always easy or even possible. For example, DataTable forces you to pass DataCells, so there is no opportunity to wrap it. Even if you can use it, it would be nicer to use the onTap and onDoubleTap callbacks that a widget may already provide.
I'd like an option to disable the onTap delay when there is also an onDoubleTap. I'm not sure the best way of doing this... some kind of global config may work, or maybe instead/also a widget level config that will need to be added to widgets that expose onTap and onDoubleTap.
I do think "fixing" this experience on desktop is important. It simply doesn't work the way users on desktop platforms expect it to.

Similar problem to @jibbers42 here: we're using ListTile, which internally uses InkWell, which derives from InkResponse, which uses GestureRecognizer.  There's no way to retrofit it with the behavior described here without reimplementing everything from selection to Material ink highlight effects from scratch.  The best approach I can immediately think of for fixing it is to introduce a widget you can wrap around a subtree to prevent onTap events from waiting for kDoubleTapTimeout.  GestureRecognizer could traverse the widget hierarchy upwards to see if there's one of those widgets present, and use that to determine its behavior.  I think that's a lot more likely to be feasible than adding a parameter to GestureRecognizer, then propagating it up to InkWell, then propagating that up to every Material widget in existence.

It's possible that https://github.com/flutter/flutter/issues/106170 should be dup'd to this one.
Here is my own workaround for this issue, in case it is helpful:
class DoubleTapInkWell extends StatelessWidget {
  const DoubleTapInkWell({super.key});

  @override
  Widget build(BuildContext context) {
    return MultiTapListener(
      onDoubleTap: () {
        // Handle double tap. Adding this handler does not cause the 300ms delay in single-taps.
      },
      child: InkWell(
        onTap: () {
          // Handle normal tap. Called on every tap.
        },
      ),
    );
  }
}

using a simple MultiTapListener widget I wrote here: https://gist.github.com/tdenniston/9197f880d2ad7acea04e36fb14d91cfc. Importantly, it does not participate in the gesture arena, which is useful for cases where you want to keep the existing single-tap handler such as with InkWell or ListTile and add on a simple extra handler for a double-tap. But its lack of participation in the gesture arena may not fit all scenarios.


update jets3t version from 0.8.1 to 0.9.4 to meet only signature v4 in cn-north-1 aws s3 region

update jets3t to 0.9.4, fix the problem alluxio can not mount aws s3 region cn-north-1 in china  , because jets3t version 0.8.1 do not support signature V4, AWS other regions support both signature V2 & V4 while cn-north-1 is a new region which only support signature V4.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16875/Failed Tests: 9org.alluxio:alluxio-underfs-gcs: 9alluxio.underfs.gcs.GCSUtilsTest.translateUserReadPermissionalluxio.underfs.gcs.GCSUtilsTest.translateUserFullPermissionalluxio.underfs.gcs.GCSUtilsTest.translateAuthenticatedUserWritePermissionalluxio.underfs.gcs.GCSUtilsTest.translateUserWritePermissionalluxio.underfs.gcs.GCSUtilsTest.translateAuthenticatedUserReadPermissionalluxio.underfs.gcs.GCSUtilsTest.translateEveryoneReadPermissionalluxio.underfs.gcs.GCSUtilsTest.translateEveryoneWritePermissionalluxio.underfs.gcs.GCSUtilsTest.translateAuthenticatedUserFullPermissionalluxio.underfs.gcs.GCSUtilsTest.translateEveryoneFullPermission
Test FAILed.

duplicate of https://github.com/Alluxio/alluxio/pull/6087


[change] Allow hot module reloading #151

closes #151

Why all the HTML files in dist/* are being committed?
I tried modifying one of those files to change the CSS color of the sidebar and then noticed it didn't take any effect, I had to modify the file in public/asset_templates/. Is what I did correct? I think so. If yes, then why are all these files being committed here? There's no need to have them, wouldn't they be automatically generated by webpack? If yes, please add a .gitignore rule which avoids these files to be committed into the repository.
The same applies to anything which is generated by webpack, let's not have build artifacts committed in the repository. When we publish the library we should publish the resulting JS file somewhere like npm and/or in the github release.

I think you are not supposed to directly modify the generated HTML files in the dist. The webpack-dev-server will work even without those in dist directory. I committed these files for the gh-pages hosting. But I'm not entirely sure if it is required.

We could do this in two steps: first do this manually by committing the artifacts in a branch, then prepare a second step (issue) in which we automate this so that we won't need to do manual steps every time we make changes to the library.

Seems appropriate to me. As gh-pages deployment is already automated we can use action like: https://github.com/peaceiris/actions-gh-pages to push build files in separate branch and changing github pages deployment to that branch (say gh-pages).


Student Explorer data purged after semester ends

Dear Dan and IT Help folks,
Request:  It appears that Student Explorer data from the Fall term has been purged in advance of the beginning of the Winter term.  For the future, we would like to request that data in the Student Explorer application from the previous term be retained a little longer --  until the day before the start of the next term.
Rationale:  After grades are posted at the end of each term, the LSA Academic Standards Board conducts our grade review to determine whether students should be placed on academic probation, be returned to good academic standing, or (in extreme cases) suspended.  In borderline cases, we would find it very helpful to be able to take at a look at a student's Student Explorer data to see the details of their class participation and grades in class assignments.
Please feel free to contact me if you need further information about this request.
Thanks in advance for your help and consideration.
Best regards,
Phil

This is being resolved by IQ to retain the data for longer

Resolved by IQ 2/28/19


Fix wrong service name when IP is node IP in k8s-mesh

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

For anyone refers to this in the future, a node ip becoming a pod ip happens in situations where a daemonset has ports exposed on hostnetwork.


updated the description on the homepage

Fixes #98
changed most of the information, but still need to make "off" in the title bolded (need to import font weight)

Jody said that she's going to make another issue to fix the fonts, as some are outdated with respect to the style guide

Jody said that she's going to make another issue to fix the fonts, as some are outdated with respect to the style guide

The new style guide still uses Poppins, so fixing it would be the right move here. But up to you.

The new style guide still uses Poppins, so fixing it would be the right move here. But up to you.


Support Microsoft SQL Server and refactored the DB classes to use parameterised queries

Created MSSQL database class. Bumped pypika to support the MSSQL pagination syntax and enforced there always being an ordering as MSSQL requires this when using pagination.
Began using parameterised queries for each database platform. Look at the database classes for each vendor to see how this is done. All platforms aside from Vertica use %(param)s syntax (Vertica uses :param).

Coverage increased (+0.3%) to 92.418% when pulling e92a38d7d4b6e18e1440391d59af1a1f843605c5 on mikeengland:db-changes into 69e9b3a008fb48b2e0a43ac3df938fe6b191fe75 on kayak:master.


Possible feature request

Hey there, I'm very sorry if this is the wrong place to write this, I am very new to runelite plugins.. Anyways I was looking for a plug in the seemed to be very close to this one, I'm smelting and was hoping for a keybind I could setup to withdraw a set amount of ore... for example, I hold F and left click on iron ore in my bank and that would make 9 (or whatever X is set to) iron ore be sent to my inventory.
It seemed like your plugin is very close to making this happen... or maybe it is able to and I'm clearly using it incorrectly... haha...
Well either way thanks for the plugin and keep up the great work!

are you asking for item-specific swaps like this? https://github.com/geheur/More-menu-entry-swaps/issues/1


Is there a param in the 'SoftImpute' function similar to 'lambda' in 'softImpute' in r?

Hi! I appreciate this work very much.
However, I notice that in the 'readme.md' file the 'SoftImpute' function is said to be inspired by the [softImpute] package for R, but there is a critical param called 'lambda', which stands for the nuclear-norm regularization parameter: \min||X-M||o^2 +lambda||M||*, not mentioned in this 'SoftImpute' function.
I am wondering whether this param can be manually adjusted if I use the function because it is important to me. Thank you if you can help!

I think it should shrinkage_value. You should initiate SoftImpute(shrinkage_value=0.1). I also implemented SoftImpute based on Julia implementation https://github.com/YagmurGULEC/py-soft-impute/blob/master/soft_impute.py.


Travel button text change

Order of the Travel button position and text(request for change) is updated matching figma.

Utils/constant file modeOfTransport is the only component object changed.

If this can be reviewed and merged ASAP it will be helpful for the next task where I have to check for specific button selection text. Thank you

Thank you for the suggestion Qing. Sean Si was saying ok with the changes
and I think he wants to get one more person to look at the changes.
If so we just need the design team to confirm the changes walk to foot.
With Taxi/ Ride Share we shall keep this as it is.
On Wed, 30 Mar 2022 at 6:43 pm, hqtan @.***> wrote:

@.**** requested changes on this pull request.
Hi @Amutha37 https://github.com/Amutha37 ,
I've left some food for thoughts to further discuss.
We can discuss online if necessary 👍
In utils/constants.js
https://github.com/CodeforAustralia/council-emissions-calculator/pull/80#discussion_r838207553
:

@@ -20,12 +20,12 @@ export const daysOfWeek = [

export const modesOfTransport = [
"Bicycle",
"Bus",

"Carpool",

"Motorbike",

"Taxi Ride",

We want to be careful about changing Taxi / ride share to Taxi Ride
Taxi / ride share means:

using taxi services to commute
using ride sharing services like Uber to commute (there might be
others)

changing to 'Taxi Ride' effectively excludes ride sharing services as an
option.
I prefer we not shorten the descriptions of transport method selections
out of 'convenience' to us, unless the shorter description still captures
the same meaning of the original description.
In utils/constants.js
https://github.com/CodeforAustralia/council-emissions-calculator/pull/80#discussion_r838213684
:

"Car",

"Motorbike/scooter",

"Taxi/ride share",

"Walk",

I prefer we use By foot instead of 'Walk' (if we need to shorten this)
at least, 'By foot' won't exclude ppl who do jog/run as part of their
commute.
⬇ Suggested change

"Walk",

"By foot",

In utils/constants.js
https://github.com/CodeforAustralia/council-emissions-calculator/pull/80#discussion_r838215561
:

"Train/tram",

"Walking/running",

"Other",

I don't think we should remove 'Other' as an option.
How will respondents respond if their transport method isn't a listed
option?
—
Reply to this email directly, view it on GitHub
https://github.com/CodeforAustralia/council-emissions-calculator/pull/80#pullrequestreview-925646735,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKV7DND7URC6KJDNQFN5MTDVCQA3ZANCNFSM5R76UJYQ
.
You are receiving this because you were mentioned.Message ID:
<CodeforAustralia/council-emissions-calculator/pull/80/review/925646735@
github.com>

Hi @Amutha37 ,
As per the discussions in Figma, let's settle on the following updates to transport method descriptions:

Add "Carpool"
"Motorbike/scooter" to "Motorbike" (as per Figma design )
"Walking/running" to "Walk/Run" (see https://www.figma.com/file/Y42AKuHDW46LiLDaTOs6sM?node-id=978:55230#172153967)
keep "Taxi/Ride Share" (see https://www.figma.com/file/Y42AKuHDW46LiLDaTOs6sM?node-id=978:55230#172154673)
exclude "Other" (see https://www.figma.com/file/Y42AKuHDW46LiLDaTOs6sM?node-id=1508:80010#175564630)

I will make the necessary updates to this PR, and merge it :+1:
Thx!

Thats the changes i have made.  Is it not ??
On Sat, 9 Apr 2022 at 10:42 am, hqtan @.***> wrote:

Hi @Amutha37 https://github.com/Amutha37 ,
As per the discussions in Figma, let's settle on the following updates to
transport method descriptions:

Add "Carpool"
"Motorbike/scooter" to "Motorbike" (as per Figma design
https://www.figma.com/file/Y42AKuHDW46LiLDaTOs6sM/Heroes-carbon-calculator-designs?node-id=978%3A54391
)
"Walking/running" to "Walk/Run" (see
https://www.figma.com/file/Y42AKuHDW46LiLDaTOs6sM?node-id=978:55230#172153967
)
keep "Taxi/Ride Share" (see
https://www.figma.com/file/Y42AKuHDW46LiLDaTOs6sM?node-id=978:55230#172154673
)
exclude "Other" (see
https://www.figma.com/file/Y42AKuHDW46LiLDaTOs6sM?node-id=1508:80010#175564630
)

I will make the necessary updates to this PR, and merge it 👍
Thx!
—
Reply to this email directly, view it on GitHub
https://github.com/CodeforAustralia/council-emissions-calculator/pull/80#issuecomment-1093529261,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKV7DNF2BGG4ABPJTSDJRQ3VEDG5PANCNFSM5R76UJYQ
.
You are receiving this because you were mentioned.Message ID:
@.***
com>


Update vk

Re-doing earlier update and tag as a pull request to facilitate proper review functionality.

This is better, but I second @GSQ-AI's comment.

@KellyVance i think i may be a bit late to the party here

@KellyVance i think i may be a bit late to the party here

@geoderekh I may be a little lax in forgetting to ever merge this. Going to have to de-conflict this at some point anyway.


drop template and local from versions; using built-in function templa…

Hello there,
would like to contribute with a small change.

dropped HashiCorp/local provider as its never used and cannot be installed on arm64 arch
using built-in templatefile() function, so template provider is not needed; furthermore, its deprecated and cannot be installed on arm64 arch

Hey, @vladborovtsov, thanks for your contribution!
Everything looks good, and Terraform version lock should be also sufficient for the function.
It's a small module, we sadly don't have any tests, and I'd like to merge it as-is.
@kobrikx could you please release a new minor version for this, when you have a chance?


Can I add plain text to steps in a feature file? Like addContext() in mochawesome!

Sample Mochawesome AddContext() code to attach any plain text with a step
Have this commands.js => cy.once('test:after:run', test => addContext({ test }, { title, value }));
I can add any text in the report/json/html by simply calling the above function like cy.addReportLog('Current is :', Current);
Do we have any option to add plain text (Show Info) to a step in cucumber json/report?

Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I'm very excited about. Furthermore, I'd like to thank @lgandecki ++ for all the work that they've done so far.
Read more about the transfer of ownership here.
The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so.


One-hot-encode categorical features in logreg

Before applying OHE it is necessary to preprocess some features as ordinal and adjust the classes labels such as in
BEFORE
1:Q - Status of existing checking account

- A11 :      ... <    0 DM
- A12 : 0 <= ... <  200 DM
- A13 :      ... >= 200 DM / salary assignments for at least 1 year

- A14 : no checking account

AFTER
1:O - Status of existing checking account

- A10 : no checking account

- A11 :      ... <    0 DM
- A12 : 0 <= ... <  200 DM
- A13 :      ... >= 200 DM / salary assignments for at least 1 year

Thus this issue was created: Ordinal features


feature: flip on dataTable.js in ip list

Pulled ip-address plugin from datatables.net.
Also, shouldn't datatable() be enabled on all tables per default ?

Is that Travis error a Django 1.9 compatibility issue?


feat: change variant inverse to neutral in spinner component

Pull Request Test Coverage Report for Build 61

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 74.068%

Totals

Change from base Build 52:
0.0%

Covered Lines:
1059

Relevant Lines:
1361

💛  - Coveralls


Update readme.md

fixes typos
FYI - The repo description also contains powerfull
Just ran across this library, can't wait to start using it! :smiley:

Thanks!


Could the json-editor have a 'help' field

This is more a feature request, but if the json-editor schema would include an optional context-help string which would appear on hovering over the html elements that would be useful, alternatively a '?' button next to the element could be provided
Cheers
Dave

Is the "description" field what you are looking for?
{
  "type": "object",
  "title": "The title",
  "description": "you could enter html in here like an <img src='question.png' />"
}

Sort of, but I think all the extra text would clutter up the form (especially if lots of explanantion is required), I think it would be better as a tooltip or that the text appears on hover over a help icon

Oh Yeh, it would also be good if html links could be added to link with other documentation

Wondering if this tooltip feature is available and how to use it? Something that gets display on mouse hover of the field.

I would like  to have this feature too.
As the description field, It would be useful if the tooltip can display html contents.
As dave said, the help button (or carret) can be interesting to show the help

One interesting feature can be only to put a caret to show or hide the description (collapsed description). So by default, all description will be collapsed, and on request you show them to the user.


[webview_flutter_web] Does not support pinch to zoom on Android

I am writing a flutter web app using this package https://pub.dev/packages/webview_flutter_web.

WebView(
            debuggingEnabled: true,
            initialUrl:
                'https://flutter.dev/',
            javascriptMode: JavascriptMode.unrestricted,
          ),

but it does not support touch pinch zoom like normal browsers do.
i am on Flutter (Channel stable, 3.0.4,) and webview_flutter_web: ^0.1.0+4

Hi @razfazz, Thanks for filing the issue. I did try the webview sample app for the web and it seems to respond to touch, pinch gesture. Please see the below output
https://user-images.githubusercontent.com/31410839/178460160-352c95e6-c69d-42e8-ad11-93047a21164b.mov

code sample
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';
import 'package:webview_flutter_web/webview_flutter_web.dart';

void main() {
  registerWebViewWebImplementation();
  runApp(const MyApp());
}

void registerWebViewWebImplementation() {
  WebView.platform = WebWebViewPlatform();
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Webview sample'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);
  final String title;
  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(
          title: Text(widget.title),
        ),
        body: WebView(
          initialUrl: 'https://flutter.dev',
          javascriptMode: JavascriptMode.unrestricted,
        ));
  }
}

flutter doctor -v (mac)
[✓] Flutter (Channel stable, 3.0.4, on macOS 12.4 21F79 darwin-arm, locale en-IN)
    • Flutter version 3.0.4 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 85684f9300 (4 days ago), 2022-06-30 13:22:47 -0700
    • Engine revision 6ba2af10bb
    • Dart version 2.17.5
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.44.0

[✓] Connected device (3 available)
    • sdk gphone arm64 (mobile) • emulator-5554 • android-arm64  • Android 11 (API 30) (emulator)
    • macOS (desktop)           • macos         • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)              • chrome        • web-javascript • Google Chrome 103.0.5060.53

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

@maheshmnj thank you for your time! I tried your code, compiled a we release version and uploaded it to my server. unfortunately it is still now working. i am testing with an android phone with chrome. what device and browser did you use to test?

@razfazz thanks for the info. I can reproduce the issue on android and it works fine on IOS. The webview cannot be scaled with the pinch gesture.

IOS
Android

flutter doctor -v (mac)
[✓] Flutter (Channel stable, 3.0.4, on macOS 12.4 21F79 darwin-arm, locale en-IN)
    • Flutter version 3.0.4 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 85684f9300 (4 days ago), 2022-06-30 13:22:47 -0700
    • Engine revision 6ba2af10bb
    • Dart version 2.17.5
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.44.0

[✓] Connected device (3 available)
    • sdk gphone arm64 (mobile) • emulator-5554 • android-arm64  • Android 11 (API 30) (emulator)
    • macOS (desktop)           • macos         • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)              • chrome        • web-javascript • Google Chrome 103.0.5060.53

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 3.1.0-0.0.pre.1594, on macOS 12.4 21F79 darwin-arm, locale en-IN)
    • Flutter version 3.1.0-0.0.pre.1594 on channel master at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 082ad11422 (2 days ago), 2022-07-11 11:40:07 +0200
    • Engine revision 2b5d5c3b2d
    • Dart version 2.18.0 (build 2.18.0-271.0.dev)
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.44.0

[✓] Connected device (3 available)
    • Redmi K20 Pro (mobile) • <IP_ADDRESS>:5555 • android-arm64  • Android 11 (API 30)
    • macOS (desktop)        • macos            • darwin-arm64   • macOS 12.4 21F79 darwin-arm
    • Chrome (web)           • chrome           • web-javascript • Google Chrome 103.0.5060.114

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

@maheshmnj thank you for reproducing. i hope this is gonna be fixed soon

it does not support touch pinch zoom like normal browsers do.

When you are comparing to other browsers, are you comparing iframe behavior (as that's what the nested webview is)?

@stuartmorgan true. so not sure if this is a feature request or a bug.

would be very nice to have this feature. it would allow displaying documents with zooming in and out

any update on this? pinch is a very important feature especially when webview is used to access Chart or Map