[ALLUXIO-51] Provide C++ binding

this commit focus on the jire task: https://alluxio.atlassian.net/browse/ALLUXIO-51

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

alluxio-bot, check this please

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/17723/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.cli.fs.command.CopyFromLocalCommandIntegrationTest.copyDirectoryFromLocalAtomic
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17724/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17725/
Test PASSed.

Jenkins, test this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17726/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17727/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17728/
Test PASSed.

@uronce-cc @yupeng9 @apc999 Please check it.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17729/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17730/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17734/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17736/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17802/
Test PASSed.

@Lichongjie thanks for taking this big project, really appreciate your effort.
Here are my high level comments before I put more detailed ones:

can we use cmake rather than autotools to manage the build? autotools is in general considered very verbose and very hard to maintain (e.g., you checked in a bunch of related files in this PR, Makefile.am, configuration.ac and many others). In contrast, for cmake, you only need a small CMakeLists.txt. One example from similar project is here
what's the purpose of alluxio-client-env.sh? is it simply setting CLASSPATH and LD_LIBRARY_PATH? if yes, I feel they should belong to the doc, rather than a script as the paths here is fixed while it can be changing over the time. In addition, you may take advantage from sourcing file libexec/alluxio-config.sh which may have the paths you need.
can you have a more detailed README? e.g., how to build this module (saw you covered this, thanks), how to run tests, how to use the library, and etc.

@apc999 thanks for your comments, here are my responses

I changed autoconf to cmake. The problem is license-maven-plugin will check the license header of CMakeLists.txt like this
`====
The Alluxio Open Foundation licenses this work under the Apache License, version 2.0
(the "License"). You may not use this work except in compliance with the License, which is
available at www.apache.org/licenses/LICENSE-2.0
This software is distributed on an "AS IS" basis, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
either express or implied, as more fully set forth in the License.
See the NOTICE file distributed with this work for information regarding copyright ownership.
====`
but cmake won't work if set this kind of header, and test will fail if other kinds of license header used in CMakeList.txt. Please give some suggestions for this problem

I already add the  CLASSPATH and LD_LIBRARY_PATH setting in readme.md.

I add more information to readme, including how to build project, how to run test functions and how to use API in other project

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/17835/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.JournalShutdownIntegrationTest.multiMasterJournalStopIntegration
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17850/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18021/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18497/Build result: FAILURE[...truncated 5088 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/target/alluxio-tests-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.jarchannel stoppedArchiving artifacts
Test FAILed.

@yupeng9  Maybe the unit test module needs to simulate alluxio runtime environment to test JNIhelper class and FileSystem API because these APIs will call alluxio API through JNI. (the alluxio-py project simple simulates alluxio server by building a http server). Is there a way to solve this problems?

@Lichongjie That's a very good question. There is minicluster program for local integration testing. Do you think you can use jni to create the minicluster for your unit testing?

Jenkins, test this please.

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/18524/Build result: FAILURE[...truncated 5225 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/target/alluxio-tests-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.jarchannel stoppedArchiving artifacts
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18526/Build result: FAILURE[...truncated 5219 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/target/alluxio-tests-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.jarchannel stoppedArchiving artifacts
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18527/Build result: FAILURE[...truncated 5171 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/target/alluxio-tests-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.jarchannel stoppedArchiving artifacts
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18528/Build result: FAILURE[...truncated 5171 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/target/alluxio-tests-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.jarchannel stoppedArchiving artifacts
Test FAILed.

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18531/Build result: FAILURE[...truncated 5191 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/target/alluxio-tests-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.jarchannel stoppedArchiving artifacts
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18532/Build result: FAILURE[...truncated 5191 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/target/alluxio-tests-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.jarchannel stoppedArchiving artifacts
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/18533/Build result: FAILURE[...truncated 5191 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/target/alluxio-tests-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.jarchannel stoppedArchiving artifacts
Test FAILed.

Merged build finished. Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18534/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18543/Build result: FAILURE[...truncated 4140 lines...][JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving<EMAIL_ADDRESS>to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pomchannel stoppedArchiving artifacts
Test FAILed.

Jenkins, test this please.

Jenkins, test this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18546/
Test PASSed.

@yupeng9 PTAL. Thanks!

@uronce-cc This c++ module is integrated by maven currently,  so how should I integrate cppcint.py in this project?

Jenkins, test this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18585/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18586/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18587/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18588/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18744/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18745/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18747/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18748/
Test PASSed.

Merged build finished. Test PASSed.

@uronce-cc @yupeng9 @apc999 PTAL, thanks

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18749/
Test PASSed.

LGTM. Thanks for adding this important feature!

@Lichongjie one comment left about the change in bin/alluxio. Otherwise this PR looks good to me


fix(completion): Give completion for local variables when pointing to whitespace

Before the closest identifier to the left of the location would be completed which meant
test   abc
//   ^ completion here would complete `test` instead of listing local variables

This fix ensures that local variables are enumerated instead.

While testing this I found that operators will be enumerated without parentheses. That is perfectly legal but it might not be what is expected.
test
//    ^ completion here will enumerate '+', '-' etc
// Is it better if it is '(+)', (-), etc ?

Copied the byte positions in the compleition tests from #115 to get the tests to pass again so I guess one of these is going to get a merge conflict.

You'll need to rebase this now - the completion API now uses byte positions, not locations.

Only after #115 is merged, we can wait with merging this until after that as I only need to delete b576cf4d7f78241bbe751aa3bac2577dd170e6f1

Oh, durp, for some reason I thought I'd finished it!


Missing dependency?

I ran the installation instructions but got
dpsanders$ python3 run_vlapy.py
Traceback (most recent call last):
  File "run_vlapy.py", line 30, in <module>
    from diagnostics import landau_damping, z_function
ModuleNotFoundError: No module named 'diagnostics'

By the way there seem to be a huge number of dependencies for what is supposed to be a simple simulation code.
I'm guessing this is due to mlflow. Perhaps that piece should be separated out and made optional somehow?

Ah sorry, I just hadn't updated run_vlapy.py after a recent refactor where the diagnostics were promoted into the main codebase.
You're right about the dependencies coming from mlflow. As you can see, the setup.py is actually quite lightweight. I think having a built-in simulation manager does wonders for workflow. It's also a very good Open Source project now supported by the linux-foundation.

The new version runs perfectly, thanks!


[Composer] Toggle connection labels

https://github.com/inmanta/web-console/assets/44098050/e4bea232-08c4-4fe8-b84c-7099fa1d2ba5
At the moment the second button in the toolbar is not doing anything. It is supposed to toggle the labels on the connections.

What's the meaning behind that labels?

It's the name of the connection. Depending on the relation it can be a from-to connection in one direction, or in two directions. Let's discuss this in the planning meeting

If it starts with an underscore, we can assume the label can be hidden

I got blocked/stuck with that problem as I got issue with proper display, distances are relative so the labes at the ends can be overflown by shapes, my solution to that base on event which isn't fired, I wrote a ticket to the jointJS team with question


Permission issue

I'm facing a premission issue.
In my .gitlab-ci.yml file tests are run by php artisan dusk... but it is executed as root.
My dusk test use a Laravel factory which create a file in storage (an image associated to an article), so this relative folder/file is created as root.
So when I try to change this file with dusk (so with www-data), I'm facing a premission issue.
Is it possible to run dusk as www-data ?
Maybe you can add sudo in the container ?

Seems works with su www-data -s /bin/bash -c "php artisan dusk --colors --debug"

By default this docker is running as root, as the vast majority of docker images.
.gitlab-ci.yml is completely customizable, so you can run dusk anylike you want, like in the example you provided.

Maybe just add sudo to simplify this.


3255 merge master back into next

Closes #3255
Summary
Merged master back into next
Change List (commits, features, bugs, etc)

Solved merge conflicts for the table related to the refactoring of table story helper functions
Solved merge conflicts for the versioning in the different package.json files, the lerna.json and the different CHANGELOG.md files.
Updated visual regression image for the table
Updated snapshots

Acceptance Test (how to verify the PR)

Verify the 4 fixes added to master after the original branch
Verify the table stories
Make sure the CHANGELOG files are correct

Regression Test (how to make sure this PR doesn't break old functionality)

Verify the table stories

Things to look for during review

[ ] Make sure all references to iot or bx class prefix is using the prefix variable
[ ] (React) All major areas have a data-testid attribute. New test ids should have test written to ensure they are not changed or removed.
[ ] UI should be checked in RTL mode to ensure the proper handling of layout and text.
[ ] All strings should be translatable.
[ ] The code should pass a11y scans (The storybook a11y knob should show no violations). New components should have a11y test written.
[ ] Unit test should be written and should have a coverage of 90% or higher in all areas.
[ ] All components should be passing visual regression test. For new styles or components either a visual regression test should be written for all permutations or the base image updated.
[ ] Changes or new components should either write new or update existing documentation.
[ ] PR should link and close out an existing issue

Great job! Table stories look good.


Suggestion: replace video caching with KTVHTTPCache and AndroidVideoCache

Currently, Caching is implemented on iOS only on AVPlayer level. Which might be problematic.
Where KTVHTTPCache for iOS and AndroidVideoCache for Android implemented video caching completely different.
They started an HTTP server and caching, loading video from there instead. It's much more stable and reliable.
I've created a react-native wrapper around them https://github.com/zhigang1992/react-native-video-cache but would love to see if you guys are interested in integration them directly from this repo?

I think this issue needs to be revisited. @zachrnolan great repo, thanks.

Raising issue @zhigang1992

I've been testing your solution and seems to work perfectly, but: Works very well on local and remote devices. Doesn't work when you stream to any local device (AirPlay). For example, stream a video on the local TV, doesn't work. It keeps loading..
Right now I've uninstalled the solution as was a pain finding the problem with my team :(. Nice work anyway

Aha, that'd actually make sense because the HTTP proxy server is hosted locally on the Phone.
If you want to be able to AirPlay, it'd probably need to do a url.replace(/localhost/, 'lan.ip') if the cache server is open to LAN access (Which I'm not 100% sure).

@zhigang1992 I tested your solution but I found that the synchronous convert method works only for short videos, 4 or 5 seconds. When I tested it with a video of length 19 seconds it fails :( Nice work anyway


Merge refs/heads/update-dependencies into alpha

Merge refs/heads/update-dependencies into alpha

This PR has been merged into alpha and tagged as 2.0.0-alpha-202308300753. Thanks for your contribution!


where the rev-manifest.json

file_get_contents(/home/vagrant/Code/Laravel/public/build/rev-manifest.json): failed to open stream: No such file or directory (View: /home/vagrant/Code/Laravel/resources/views/index.blade.php)

you should run npm install (or run bower install && gulp --production) with non root user.

The truth has been spoken :+1:

thx


[Springer] Add Pflügers Archiv to extra list

This fixes https://github.com/citation-style-language/styles/issues/1578
which was manually solved by
https://github.com/citation-style-language/styles/pull/1581

(
Note, I can currently not run the Ruby script on my Springer folder, because an error occurs:
$ ruby generate_styles_from_data.rb -d springer
Script: C:/Users/zumstein/Coding/utilities/generate_dependent_styles
Input:  C:/Users/zumstein/Coding/utilities/generate_dependent_styles/data
Output: C:/Users/zumstein/Coding/utilities/generate_dependent_styles/generated_styles

Generating styles...
generate_styles_from_data.rb:21:in `gsub!': incompatible character encodings: CP850 and UTF-8 (Encoding::CompatibilityError)
        from generate_styles_from_data.rb:21:in `title_to_styleID'
        from generate_styles_from_data.rb:271:in `block (2 levels) in <main>'
        from generate_styles_from_data.rb:230:in `each'
        from generate_styles_from_data.rb:230:in `block in <main>'
        from generate_styles_from_data.rb:167:in `each'
        from generate_styles_from_data.rb:167:in `<main>'

)

Does it work without the changes from this PR?

No, it didn't work before and is not working afterwards. I think it is a character encoding problem. All my files should be encoded in UTF8. However, I don't know where the CP850 is coming from...

Were you on Windows? Otherwise, you could try to run this on the Springer files: http://stackoverflow.com/questions/115210/utf-8-validation

Yep, I am on Windows.

Okay, I can produce the files with
 ruby --external-encoding UTF-8 generate_styles_from_data.rb -d springer

It works fine and creates 2022 styles and the new Pflüger style looks correctly.

Thanks!


Added as_super and into_super methods for Bound<T: PyClass>

This PR adds two new methods to provide a more convenient mechanism for casting a Bound pyclass to its base type. The new methods mirror the corresponding methods for PyRef and PyRefMut (see #4219).
Casting Bound<T> to Bound<T::BaseType> can be useful in the context of the PyMyClassMethods idiom when an extension trait is use to implemented methods (for use from Rust) on the Bound version of a pyclass's base type. The upcast of a pyclass to its base type is a trivially safe operation, but making this cast is currently extremely verbose.
For example, there are currently two options for casting Bound<T> to Bound<T::BaseType by value:
// 3 method calls including an unnecessary `unwrap`
let sub: Bound<SubClass> = /* ... */;
let _ = sub.into_any().downcast_into::<BaseClass>().unwrap();
// or 2 method calls using `unsafe`
let sub: Bound<SubClass> = /* ... */;
let _ = unsafe { sub.into_any().downcast_into_unchecked::<BaseClass>() };

Upcasting by reference is a bit less painful since you can leverage Deref<Target=PyAny> to avoid the first method call, but its still ugly and requires either an unwrap or an unsafe block.
The new methods added by this PR make it much nicer:
let sub: Bound<SubClass> = /* ... */;
// upcast by reference
let _= sub.as_super();
// upcast by value
let _ = sub.into_super();

Good catches, thanks!


[WIP] [Beam-3032] - Add RedshiftIO

A IO allows users to:

Bulk upload data from S3 into Redshift
Write data from PCollection to Redshift
Read data out of Redshift

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Hi @iemejia and @aromanenko-dev, I got a few questions want to discuss with you two:

The Copy part of this IO, I am thinking if we should put it in the RedShift class file as? together with Write and Read? and rename it to RedShiftIO to be consistent with the other IOs? It’s kind of weird if we have org.apache.beam.sdk.io.aws.redshift.Redshift.Write and org.apache.beam.sdk.io.aws.redshift.Copy, right?
Second, in the Write, currently it writes to S3, then copy to Redshift. Should we write directly to Redshift? I have also implemented Postgresql sink for my internal use which just use postresql dirver to write to Redshift. So wondering if we should do this way?
I had the same issue with the com.amazon.redshift.jdbc.DataSource when I implemented the my Postgresql Sink. so I had to use progress driver. Redshift is actually based off postgresql, so it supports JDBC --> we’re safe to use it. But, if we want to use this Redshift driver, it’s going to a problem for unit test, because the test need to load/provide this class to run the Write/Copy?
As we discussed, Ismael, I can bring in Localstack to writing unit tests, but localstack hasn’t supported AWS SDK V2 yet. So I guess we have to stick with V1 for now?

Please let me know what you think?

@cmachgodaddy Are you going to continue work on this? Do you have any principal obstacles for that? Is any help needed?

Yes, Sir. I am working on it, and hitting authentication issue. More specifically, Redshift need to have permission to access S3, and because of my restrict role on Aws account, I can't grant that permission for the app. Second issue, the Copy/Redshift IO is authenticating to S3 using access key and secret, which are not supported in with my account, so I am adding IAM Role to for this authentication instead.


Make built-in MDC key req.id give requestId of root ServiceRequestContext

Currently, MDC key, req.id, evaluates to requestId of ClientRequestContext even if it has ServiceRequestContext as its root. This undermines the benefit of using MDC as the logs within ClientRequestContext don't leave any contextual information of which service request they are scoped to.
I wonder if this is an intended behavior and I should introduce a custom MDC key to trace client logs within a span of service request.
If not, a simple fix for BuiltInProperty.REQ_ID will do the work:
// AS-IS
REQ_ID("req.id", log -> log.context().id().text())

// TO-BE
REQ_ID("req.id", log -> log.context().root() != null ? log.context().root().id().text()
                                                     : log.context().id().text())

A request ID is designed to assign a unique key to every request. Therefore I don't think we can use a request ID as a trace ID.
If users need to group a set of requests which are created at the same scope of a ServiceRequestContext,
how about adding a new property such as "req.traceId" or "req.rootId"(need a better name) for that purpose?

Yeah, we need a new property for the purpose.
Because of the root() of a ClientRequestContext could be null(the new property doesn't return null when the root() is null), I slightly prefer to use req.trace_id.
I'm worried about if there's someone who already uses the name though.

Request ID is not a trace ID to be precise, so rootId sounds better to me.

Yeah, but ClientRequestContext.root() returns null if the ctx is created when there's no ServiceRequestContext in the thread local.
But the new property needs to return the id of the ClientRequestContext in such a case.
Isn't okay with that? Or should we change to return the ClientRequestContext when ClientRequestContext.root() returns null?

I think we should return null when ServiceRequestContext is null if we go with req.rootId.

Ah, yeah, that makes sense. Any better names?

req.rootOrSelfId ? :laughing:

req.root_id will be enough to serve my needs! Collecting only the ID of ClientRequestContext is of no use in our ordinary use cases. Can I work on adding the new built-in property?

@ks-yim Yeah, thanks a lot in advance!

Just make sure that req.root_id return null if ClientRequestContext.root() returns null. Is that right?

Just make sure that req.root_id returns null if ClientRequestContext.root() returns null. Is that right?

Right, I will work in that way!


⚠ Exoticaz has degraded performance

In c0f0272, Exoticaz ($EZ) experienced degraded performance:

HTTP code: 200
Response time: 4613 ms

Resolved: Exoticaz performance has improved in 500b3d8.


MEMS Inc. Edits and Old Doc Uploads

I've fixed some formatting things in the MEMS and added TML to the main navigation. Take a look at those changes as they're good patterns for the TML docs. We can go over setting up a local server on your machine so you can see renders before pushing.


Permanent caching?

Hi,
I have an issue where feature flags appear to be permanently cached throughout the lifetime of the ASP.NET Core session.
WebApi.cs file has:
 return new WebHostBuilder()
                                    .UseKestrel()
                                    .ConfigureAppConfiguration((builderContext, config) =>
                                    {
                                        config.AddJsonFile(environment, serviceContext);
                                        var settings = config.Build();
                                        AppConfigExists = !string.IsNullOrWhiteSpace(settings["VDSSettings:AppConfig"]);
                                        if (AppConfigExists)
                                        {
                                            config.AddAzureAppConfiguration(options => {
                                               options.Connect(settings["VDSSettings:AppConfig"])
                                                      .UseFeatureFlags();
                                            });
                                        }
                                    })

UseFeatureFlags had CacheExpirationTime set at one point (not above) but it didn't seem to make a difference.
The ASP.NET core web API is hosted in Service Fabric on Azure.
To reproduce:

Make a request
Feature flags are set as expected (in the App Configuration on Azure) - can see from a log in App Insights
Change the flag
Wait 30 seconds (or an age)
Make a request
Feature flag has not changed

From my machine (running Service Fabric locally), it's as above. However, I can get different behavior if I follow the steps below:

Change the flag
Stop debugging
Start debugging again
Make a request
The flag will have the updated value

In the controller files I'm using IFeatureManagerSnapshot. I get a flag by using something like:
_enable = await _featureManagerSnapshot.IsEnabledAsync(FeatureFlagConstants.Enable);
So it appears as though the cache isn't getting released as I'd expect it to, but holds the values for the lifetime of the software being in memory.
Version info:
FeatureManagement 2.0.0
FeatureManagement.AspNetCore 2.0.0

Are you calling UseAzureAppConfiguration as mentioned in this document to set up dynamic updates from Azure App Configuration? https://docs.microsoft.com/en-us/azure/azure-app-configuration/enable-dynamic-configuration-aspnet-core?tabs=core2x#reload-data-from-app-configuration

I'm experiencing the same problem, also using Service Fabric to host the application. I can only get the flag to have the updated value if I restart the application in Service Fabric. I'm also using v 2.0.0 of the FeatureManagement packages and v 3.0.2 of AzureAppConfiguration. My code does call UseAzureAppConfiguration as indicated above.

For further context, my application is a Hosted Service so there is no middleware. I see that Azure App Configuration provides a refresher that can be used in such cases - does something similar exist for feature flags?

I'm about to try to repro this, but one thing I can point out from the initial issue description is that after making the request after waiting 30 seconds it is expected that the feature flag wouldn't have changed. That's because that request triggers the application to check for any updates from Azure App Configuration. So there would have to be one more request to see the changes.

I just ran the FeatureFlagDemo app that's included and pointed to the v2.0.0 version of the libraries. It is behaving as expected. Can you take a look at my previous comment and see if it helps?

I was lacking the UseAzureAppConfiguration method but adding it didn't resolve the problem. (I sure was excited for a little while though).
@jimmyca15 I'm not sure why I'd need another request to see the changes. I'll explain a bit more:
If I change the feature flag in Feature Management on Azure, then on the next request to my SF app, I expect the _featureManagerSnapshot to check to see if the cache has expired (when the flag setting is being queried by my app) and then get the update from AppConfig if the cache time has indeed expired. I've done a lot of testing with many other tests with the SF session still running. It doesn't matter how long I wait (even the next day) or how many times I make the same request, the flag doesn't update. Restart SF, however, at it get the correct value straight away.
Maybe it's a SF problem.

@ledpup
Service fabric shouldn't be a factor. If you are running an ASP.NET Core application the hosting platform should be irrelevant. I was unable to repro this with the example FeatureFlagDemo app, but if you are able to provide a minimal repro ASP.NET Core app, I could make sure everything is wired up correctly or perhaps be able to repro it.
@evelynnkaplan
The refresher that you mentioned is also able to refresh feature flags.

Hi @jimmyca15, I've stripped out as much as I can for my SF-based implementation of feature flags and put it into a repo. It's at https://github.com/ledpup/ff-demo.
ProgramController.cs get the FF from AppConfig.
The endpoint is set in appsettings.Development.json (replaced with junk).
"app.UseAzureAppConfiguration();" and "services.AddFeatureManagement();" is in Startup.cs
WebApi.cs does the connection
Thanks so much for your time.

Hi @jimmyca15, just thought I'd try bumping on this issue. I haven't found a solution to the problem.

Hello @ledpup
I took a look at your repro. I can see that it is stripped down, but it is still intertwined with Service Fabric so I haven't been able to find time to get it set up and that's why I haven't been able to get back yet.
That being said after looking at the code everything looks good, and now I do suspect that somehow Service Fabric is playing a part in this. There are two things I would test.

Use IFeatureManager instead of IFeatureManagerSnapshot
Check if Service Fabric is disposing services in the service collection.

#1 is easy, #2 requires a bit of playing around to see if Service Fabric is doing something unexpected there. The feature management system relies on a change token, which is disposable, to pick up configuration changes. If service fabric is somehow disposing things then this problem could occur. If I could get the app running on service fabric I would test this by adding my own custom simple class that implements IDisposable to the applications services, get it in a controller and log if it ever gets disposed. Haven't found a chance to get anything running on service fabric though, and not sure when I will be able to.

Hi @jimmyca15 ,
I tried test 1. It didn't work with IFeatureManager either.
I tried test 2 by adding a basic class that can IDisposable to the DI container. I tried as a singleton and a transient and put a breakpoint on dispose. Singleton stayed alive between requests. Transient disposed on each request. It appears to function as I'd expect.
I committed them to https://github.com/ledpup/ff-demo if you want to review.

I'm seeing the same permanent caching issue. Here's a pared down example that I can reproduce it with: https://github.com/dmacdnld/feature-flags-test/.

I'm seeing the same permanent caching issue. Here's a pared down example that I can reproduce it with: https://github.com/dmacdnld/feature-flags-test/.

I'm seeing the same permanent caching issue. Here's a pared down example that I can reproduce it with: https://github.com/dmacdnld/feature-flags-test/.

I'm seeing the same permanent caching issue. Here's a pared down example that I can reproduce it with: https://github.com/dmacdnld/feature-flags-test/.

I had the same issue where Feature Manager would only return the features defined when starting the app. Any subsequet calls would not get the latest enabled features and would return the original features.
I had to add a singleton of the Configuration in program.cs in order to get the Feature Manager to work.
                webBuilder.ConfigureServices((hostingContext, services) =>
                {
                    services.AddSingleton(hostingContext.Configuration);
                });

My startup.cs looks like this: public Startup(IConfiguration configuration)
{
Configuration = configuration;
}`
@jimmyca15 Do you have any idea why I needed to inject the singleton of the Configuration? I didn't see this in the demo.

Had very similar issue. IConfiguration value was updating as expected, but IFeatureManager permanently returned value that was set on app start.
Turns out, it was caused by services.AddApplicationInsightsKubernetesEnricher();. I'm running locally using docker compose, but plan to migrate to Kubernetes. Very weird side effect.

I had the same issue where Feature Manager would only return the features defined when starting the app. Any subsequet calls would not get the latest enabled features and would return the original features.
I had to add a singleton of the Configuration in program.cs in order to get the Feature Manager to work.
                webBuilder.ConfigureServices((hostingContext, services) =>
                {
                    services.AddSingleton(hostingContext.Configuration);
                });

My startup.cs looks like this: public Startup(IConfiguration configuration)
{
Configuration = configuration;
}`
@jimmyca15 Do you have any idea why I needed to inject the singleton of the Configuration? I didn't see this in the demo.

It's difficult without a simple repro application. It could be possibility that the application code is doing something with a separate configuration provider than the feature manager is seeing.

Had very similar issue. IConfiguration value was updating as expected, but IFeatureManager permanently returned value that was set on app start.
Turns out, it was caused by services.AddApplicationInsightsKubernetesEnricher();. I'm running locally using docker compose, but plan to migrate to Kubernetes. Very weird side effect.

Removing this fixed it for me too!! Crazy!

@kev24uk
There was an issue with the AddApplicationInsightsKubernetesEnricher method that broke configuration updates at runtime. An issue was filed for it, and it looks like it should be fixed with version 2.0.2.
Details here: https://github.com/microsoft/ApplicationInsights-Kubernetes/issues/236

Issue hasn't had any updates. Please feel free to ping if there's still any concerns.


clang-format: Extend default line length

Line length of 80 characters is too short in several cases where nested statements are used and long variable names cause the line to be wrapped and makes the code less readable.  Additionally, most tools (vscode, etc) allow for showing far more than 80 characters per line.

We are not making format changes until a publicly available style guide has been published and approved.

We are not making format changes until a publicly available style guide has been published and approved.

Please treat this as merely a suggestion/proposal that matches my preferences.

Personally, I often end up working in windows that are <100 columns wide, so I tend to prefer an 80 column limit.
When we work on the style guide, I would be open to reviewing specific code examples where 80 columns is making the code harder to read, alongside comparisons of other column width limits for the same code.


Develop

Update api keys

Sorry for accidentally creating this pull request. I was playing around with my own hosting.


time-dependent cox regression model

will you implement time-dependent cox regression model? This is more meaningful than pure cox regression model.

This is planned for the next release, and I'll likely start late next week.

[ ] https://cran.r-project.org/web/packages/survival/vignettes/timedep.pdf
[ ] http://www.math.ucsd.edu/~rxu/math284/slect7.pdf
[ ] http://www.annualreviews.org/doi/pdf/10.1146/annurev.publhealth.20.1.145
[ ] https://socialsciences.mcmaster.ca/jfox/Books/Companion/appendix/Appendix-Cox-Regression.pdf


Allow more time between reconnection attempts in the dialer

Recent logs in the taker showed that we could have accidentally hammered the maker with a lot of unnecessary requests when the maker was already trying to process a connection request from the dialer.

bors r+


[TOMEE-4185] Dependencies cleanup, branch 8.x

improving pom quality by:

[x] ordering dependencies
[x] adding properties for versions
[ ] removing unused dependencies
[ ] upgrading dependencies when there is multiple versions for single dependency

doing this allows to detect problems like versions inconsistencies
this PR is ready and others tasks needs to be done in separate PRs

8.x is eol now.


⚠ Fortnite has degraded performance

In 7144258, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1600 ms

Resolved: Fortnite performance has improved in 2831979.


tsudo removes quotes from commands

$ tsudo 'mkdir 'test1 test2''
$ ls -l
test1
test2

Correct output should be one directory with the name 'test1 test2', not two directories.

Thank you! I wrongly assumed that you can nest single quotes in bash from the fact that double quotes are nestable.
On May 19, 2018 2:25:01 AM GMT+02:00, tinydynamite wrote:

If you used single, outer quotes when typing the command in your
terminal the inner quotes should have been double, otherwise
$SHELL will resort to word-splitting.

This has to do with how the shell handles arguments.. and not with tsudo itself..
I'm glad you found the solution...
Closing this for now


Add transmission sensor: number of active torrents

Description:
This pull request adds a new sensor type for the transmission platform, to get the number of active torrents.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#3655
Example entry for configuration.yaml (if applicable):
sensor:
   - platform: transmission
     host: IP_ADDRESS
     monitored_variables:
       - 'current_status'
       - 'download_speed'
       - 'upload_speed'
       - 'active_torrents'

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

Hi @mclem,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


fix prefix search first seen

prefix search: populate first_seen on first_imports, here and elsewhere
ex: https://dns.coffee/search/prefix/active/NIC
Can use first_import as first_seen for zones because all the new TLDs where created after I started indexing the root. (double check that the logic fully applies).

The issue here is to fix the blank or missing "First Seen" dates.
In the DB schema, I leave first_seen null if the record was present on the first import for the given zone, and the zone was not newly created (in DNS). However, for only the purposes of this search prefix page, we can populate the missing "First Seen" fields with the dates of the first import for the zone.


📝 Update includes for docs/tutorial/relationship-attributes/cascade-delete-relationships.md

📝 Update includes for docs/tutorial/relationship-attributes/cascade-delete-relationships.md

Thanks for the effort! This was covered in another PR, so I'll close this one now. :coffee: :cake:


Calculating wrong date

Hi. I use your library for my project. I convert Western Day to Tibetan day and I found the error. Example 7/11/2022 -> 13/9/2149, exactly 14/9/2149. https://www.lotsawahouse.org/Cgi/phugpa.pl

Hi @SolveMyProblem ,
As I checked with same date, I couldn't able to replicate the issue.
tibDate =TibetanCalendar.getTibetanDate(DateTime(2022, 11, 7));
print(tibDate.day); // print 14
print(tibDate.month); // print 9
print(tibDate.year); // print 2149

Please check and let me know


🚀 : User Rating System

Idea
As a user, it would be great to know with one look at a users profile how willing they might be to engage in meaningful conversations and help you and others in learning your target language(s). A rating system for users, where you could give users a rating based on there kindness, willingness to converse, and helpfulnesses would be really useful.
How it will help
Not only would it help you choose who you’d like to spark a conversation with, but it would also provide further motivation to users to put their best foot forward when chatting on LangX.
Implementation Ideas
To prevent spam, you could limit rating to those who have chatted with the person they wish to rate for at least X amount of time or after X amount of messages.

Thank you for raising that issue.
We appreciate your suggestion for a user rating system based on kindness, willingness to converse, and helpfulness. This feature could indeed enhance the experience by helping users identify potential conversation partners who are more likely to engage meaningfully and support language learning efforts. Additionally, it would motivate users to contribute positively to the community.
To prevent spam and ensure fair ratings, we could implement a restriction where users can only rate others after having interacted with them for a certain amount of time or after exchanging a specified number of messages.
Thank you for your valuable input! @binbang12

duplicate of #491?

duplicate of #491?

I think its related with it but not duplicated. Thank you linked with that issue as well


Add the possibility to expand and compress each main entry in the database tree block

Each menu entry started with the caracter ">" is a menu that has to be able to expand and collapse.

In the image above, for example, every database and every "Collections", "Views" and "Users" will have to be able to expand/collapse with the 'Enter' key.
This will make the information more succinct, showing only what I want to see. And will be useful for cluster that has a lot of databases.
Another thing that will probably need to be changed is the way that each item is displayed. Each one is nested by just space characters. Like this: L97, L105, L113. I feel like there's a better way to nested these items.
Tasks

[x] Make each menu item to be expandable
[x] Handle the nested items better

tui-rs don't have an official widget for tree objects, and it would be very complex for me to create one from scratch. That was the main issue with doing it with Rust, tview supports it, so I've decided to use go instead.


Feature/image sources

closes #176
closes #106

Codecov Report

Merging #263 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #263      +/-   ##
===========================================
+ Coverage    99.15%   99.15%   +<.01%
===========================================
  Files           87       87
  Lines         4016     4020       +4
===========================================
+ Hits          3982     3986       +4
  Misses          34       34


Subqueries cannot reference relations

First, I'm running objection v0.8.8.
This example is a bit contrived, but say I want all users who have young pets ordered by their account creation dates.  Consider the following query,
const resultQuery = Users.query()
    .joinEager('pets')
    .where('pets.age', '<', 2)
    .groupBy('Users.id');

const usersWithYoungPets = await Users.query().from(resultQuery).orderBy('createdAt');

This fails with the following stacktrace,
TypeError: Uncaught error: Cannot read property 'columns' of undefined
at RelationJoinBuilder.buildSelects (/project/node_modules/objection/lib/queryBuilder/operations/eager/RelationJoinBuilder.js:355:58)
at RelationJoinBuilder.doBuild (/project/node_modules/objection/lib/queryBuilder/operations/eager/RelationJoinBuilder.js:255:12)
at RelationJoinBuilder.build (/project/node_modules/objection/lib/queryBuilder/operations/eager/RelationJoinBuilder.js:112:10)
at JoinEagerOperation.onBuild (/project/node_modules/objection/lib/queryBuilder/operations/eager/JoinEagerOperation.js:51:22)
at QueryBuilder.buildInto (/project/node_modules/objection/lib/queryBuilder/QueryBuilderOperationSupport.js:177:10)
at buildInto (/project/node_modules/objection/lib/queryBuilder/QueryBuilder.js:1096:25)
at QueryBuilder.build (/project/node_modules/objection/lib/queryBuilder/QueryBuilder.js:458:19)
at convertQueryBuilderBase (/project/node_modules/objection/lib/queryBuilder/operations/ObjectionToKnexConvertingOperation.js:93:18)
at convertArgs (/project/node_modules/objection/lib/queryBuilder/operations/ObjectionToKnexConvertingOperation.js:43:16)
at FromOperation.onAdd (/project/node_modules/objection/lib/queryBuilder/operations/ObjectionToKnexConvertingOperation.js:23:17)
at FromOperation.onAdd (/project/node_modules/objection/lib/queryBuilder/operations/FromOperation.js:17:23)
at QueryBuilder.addOperation (/project/node_modules/objection/lib/queryBuilder/QueryBuilderOperationSupport.js:134:33)
at QueryBuilder.from (/project/node_modules/objection/lib/queryBuilder/QueryBuilder.js:971:17)
at my project code

The issue is that the before2 JoinEagerOperation hook required to generate the query (by fetching column names) would be called to execute the subquery (though naturally we're not executing it) but is not called just to build the subquery.

You could try something like a join distinct, since you're not interested in eagerly fetching the pets data anywhere:
const idColumn = 'Users.id';

const filterQuery = Users
  .query()
  .distinct(idColumn)
  .joinRelation('pets')
  .where('pets.age', '<', 2);

const usersWithYoungPets = await Users
  .query()
  .innerJoin(
    filterQuery.as('filter_query'),
    idColumn,
    'filter_query.id'
  );

That's a good idea, thanks!  I have worked around my issue now as I didn't really need all those columns, but I still think it might be worthwhile to investigate a fix for this.

There's no easy way to fix this and @jeff3yan is right, you should use joinRelation instead. It's just like joinEager but without the output mapping into a tree of models. joinEager doesn't really make sense as a subquery.


Fix compile.

Would in theory close #6

It complains that it doesn't have any sort of gossip menu attached if you try to compile with the gossip_menu_id not set to 0. Haven't tested it at all because I've been troubleshooting other modules as well, so I'm leaving my progress here if anyone wants to take a look and test it before I take a deep look.

Closing as I credited you and port your draft over earlier. Thanks for hte assistance once again.


simplyadmire submodule missing

C:\Users\xmr\Desktop\Cloudflare-WordPress>git submodule init
fatal: No url found for submodule path 'vendor/simplyadmire/composer-plugins' in .gitmodules

It seems .gitmodules is missing in https://github.com/cloudflare/Cloudflare-WordPress/commit/46b721f8da44c935be413ef4aa8eb996e27819f2
Is that even needed? Tests seem to pass.
/CC @jwineman @thellimist

Is that even needed? Tests seem to pass.

vendor/simplyadmire/composer-plugins is not a necessity. It can be removed.

Can you remove it and any references from composer files too?

Correction: simplyadmire/composer-plugins is used by wimg/PHPCompatibility
For more info check:
https://github.com/wimg/PHPCompatibility/
I don't know the issue with git submodule init though. We'll need to discovered that.

If we remove wimg/PHPCompatibility as part of the deployment process we can just update trim_code_for_release.sh to remove this too if PHPCompatibility is the only thing that depends on it.

@jwineman: My main concern is how is it needed? When one clones the repo, they end up with an empty submodule. So, I can't see how it is really needed...

Yeah I agree.  Its a dependency of wimg/PHPCompatibility but since we remove wimg/PHPCompatibility during the deployment process we can also remove simplyadmire/composer-plugins.

Closing the issue since trim_code_for_release already has the removal code for deployment


docs: update API ref link in README

Title says it all

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@edc5a16). Click here to learn what that means.
 Consider uploading reports for the commit 9adb74d to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #361   +/-   ##
=======================================
  Coverage        ?   36.89%
=======================================
  Files           ?       17
  Lines           ?     4458
  Branches        ?      166
=======================================
  Hits            ?     1645
  Misses          ?     2811
  Partials        ?        2

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Testsuite setup errors

Describe the bug
When I used cookiecutter and check the testsuite, I found two different problems.
When running tox locally:

sphinx dependency is not pulled into tox environment which raise the following exception: ImportError: Error importing plugin "sphinx.testing.fixtures": No module named 'sphinx'

flake8 reports an error in cookiecutter/{{cookiecutter.project_name}}/sphinxcontrib/{{cookiecutter.package_name}}/init.py:
# type: (Sphinx) -> Dict[unicode, Any], unicode is not recognized and raise a F821 error

More logs in the attached file: testsuite_errors.log
To Reproduce

Create a virtualenv: python -m venv env
Source it: source env/bin/activate
Install cookiecutter: pip install cookiecutter
Create a dummy extension using cookiecutter: cookiecutter https://github.com/sphinx-contrib/cookiecutter.git
Install tox and run it

Expected behavior
I expect the testsuite to fail because there is no tests.
Environment info

OS: Linux (Archlinux)
Python version: 3.8.2
cookiecutter version: master (d02c0d662e3d54a3a1abbd98d1b4074df9eb0b1c)

Additional context
As described above, I used a python virtual environment.

Resolves in #4


MacOSX / QTKit capture: trying to fix invalid timer call

The same as #6051, which solved #5874, but this one is for old branch 2.4. Works for me. Since many developers are still working on 2.x so might be useful.

:+1:


I want eager loading whitout  query filter, how can i do?

I want eager loading whitout  query filter, how can i do?
why eager loading use query filter default?
SELECT `m`.`MeetingId`
FROM `InsideAttendee` AS `m`
INNER JOIN (
    SELECT `m0`.*
    FROM `Meeting` AS `m0`
    WHERE (`m0`.`IsDeleted` = 0) AND (`m0`.`TenantId` = @___tenantId_0)
) AS `t` ON `m`.`MeetingId` = `t`.`Id`
WHERE (`m`.`IsDeleted` = 0) AND (`m`.`TenantId` = @___tenantId_0)

I want like this
SELECT `m`.`MeetingId`
FROM `InsideAttendee` AS `m`
INNER JOIN (
    SELECT `m0`.*
    FROM `Meeting` AS `m0`

) AS `t` ON `m`.`MeetingId` = `t`.`Id`
WHERE (`m`.`IsDeleted` = 0) AND (`m`.`TenantId` = @___tenantId_0)

use IgnoreQueryFilters result
SELECT `m`.`MeetingId`
FROM `InsideAttendee` AS `m`
INNER JOIN (
    SELECT `m0`.*
    FROM `Meeting` AS `m0`

) AS `t` ON `m`.`MeetingId` = `t`.`Id`

@2501272126 It seems that you are asking for the query filter to be disabled for one entity type while still being enabled for another entity type. This is not something we plan to implement. Instead, you should either make your query filters more dynamic, or inline the filtering with the query rather than using a global filter.

I think global query filter work with Include is meaningless.
It's not include filtering.
When i including related entities, I'm not care it is soft deleted or not.
That's include filtering's work


Update to :v1_1 casks with new helpers

Forgot about this when merging #12983 and #12984.

LGTM :+1:

Merged as 56feb3f501ed3496c96c12c116fa8d51ca06af80.


layout practice

https://tympanus.net/codrops/2019/06/04/inspirational-websites-roundup-5/
http://every-layout.dev

I am confused about every-layout.dev, because there are sections you have to pay for?!

From its website:

large selection of free content, including all of the “rudiment” articles that cover the basics of (our take on) contemporary CSS

You only have to pay if you want a very comprehensive version.
I think it looks cool as hell. @sw-yx: May I ask what stopped you from adding this?

nothing, i was just on mobile at the time 😅  and i dont think i had a layout section back then. its added now

what about https://csslayout.io/?

ooh, i like this! adding. thanks @bboydflo