[ALLUXIO-3201] Log results of server configuration checker

https://alluxio.atlassian.net/browse/ALLUXIO-3201
Example result:
Passed:

Warn:

Failed:

@aaudiber @apc999 PTAL, thanks!

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/19643/Build result: FAILURE[...truncated 2373 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-keyvalue-common/1.8.0-SNAPSHOT/alluxio-keyvalue-common-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/checker/pom.xml to org.alluxio/alluxio-checker/1.8.0-SNAPSHOT/alluxio-checker-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/pom.xml to org.alluxio/alluxio-core-client-fs/1.8.0-SNAPSHOT/alluxio-core-client-fs-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.8.0-SNAPSHOT.jar to org.alluxio/alluxio-core-client-fs/1.8.0-SNAPSHOT/alluxio-core-client-fs-1.8.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-client-fs/1.8.0-SNAPSHOT/alluxio-core-client-fs-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.8.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-client-fs/1.8.0-SNAPSHOT/alluxio-core-client-fs-1.8.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/pom.xml to org.alluxio/alluxio-core-common/1.8.0-SNAPSHOT/alluxio-core-common-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.8.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.8.0-SNAPSHOT/alluxio-core-common-1.8.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.8.0-SNAPSHOT/alluxio-core-common-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.8.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.8.0-SNAPSHOT/alluxio-core-common-1.8.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.8.0-SNAPSHOT/alluxio-core-server-worker-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.8.0-SNAPSHOT/alluxio-logserver-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.8.0-SNAPSHOT/alluxio-core-client-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.8.0-SNAPSHOT/alluxio-examples-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.8.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.8.0-SNAPSHOT/alluxio-examples-1.8.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.8.0-SNAPSHOT/alluxio-examples-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.8.0-SNAPSHOT/alluxio-core-1.8.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.8.0-SNAPSHOT/alluxio-core-server-proxy-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.8.0-SNAPSHOT/alluxio-shell-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.8.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.8.0-SNAPSHOT/alluxio-shell-1.8.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.8.0-SNAPSHOT/alluxio-shell-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.8.0-SNAPSHOT/alluxio-tests-1.8.0-SNAPSHOT.pomchannel stoppedArchiving artifacts
Test FAILed.

@aaudiber I agreed to log nothing when the ConfigStatus is PASSED.
Actually, I would prefer only to log ConfigStatus like Status: WARN/ERROR and do not print any inconsistent property details.
In the config checker integration test, when all the nodes have different log files and conf files, the master.log of leader master is so messy. When we have 6 nodes, the inconsistent properties can fill half of the screen. If we have thousands of nodes. the master.log will be really noisy.
maybe we can write something like
ServerConfigurationChecker -- Status: WARN(please go to the web UI or run fsadmin doctor CLI to get inconsistent property details
or just ：
Status: WARN
Status: ERROR
Thanks!

How does this sound? The first time we detect warnings/errors, we log them and point the user to the web UI/fsadmin doctor. After that, we don't log anything when the report is updated
We can also add a thread to check the report once an hour and log the warnings/errors if there are any, and/or direct the user to the UI/CLI

If we log warnings/errors at the first time we detect them, it may only detect a small subset of the warnings/errors.
For example, we have a cluster of 10000 nodes. When two nodes register their conf with the leader master, we could detect errors and warnings and log them.
If we log them when the report is updated, the logs can also be messy because the report is updated when new nodes come in.
In the cluster of 10000 nodes, the config check report may keep updating (the inconsistent properties will be updated) and the logs will be filled with warnings/errors.
The best approach would be to log the report when we get all the nodes registered but the leader master is not able to know the cluster size.
I will prefer to log when the configStatus changed and direct the users to use the webUI/ CLI. In the meantime, if the log time gap is bigger than one hour and configuration errors/warnings exist, we log them.
@aaudiber What's your opinion on this approach?

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

Build finished. Test PASSed.

@aaudiber @apc999 I updated the config report log to support

log when config check status changes
periodic log the report (set to 1hour now)
add help info to direct users to web UI or fsadmin doctor CLI.

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

@aaudiber Addressed the comments, PTAL, thanks.

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/19730/
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/19732/
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/19737/
Test PASSed.

@apc999 this PR has changed quite a bit, are you still LGTM for it?

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/19748/Build result: FAILURE[...truncated 2139 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-keyvalue-common/1.8.0-SNAPSHOT/alluxio-keyvalue-common-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/checker/pom.xml to org.alluxio/alluxio-checker/1.8.0-SNAPSHOT/alluxio-checker-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/pom.xml to org.alluxio/alluxio-core-client-fs/1.8.0-SNAPSHOT/alluxio-core-client-fs-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.8.0-SNAPSHOT.jar to org.alluxio/alluxio-core-client-fs/1.8.0-SNAPSHOT/alluxio-core-client-fs-1.8.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-client-fs/1.8.0-SNAPSHOT/alluxio-core-client-fs-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.8.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-client-fs/1.8.0-SNAPSHOT/alluxio-core-client-fs-1.8.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/pom.xml to org.alluxio/alluxio-core-common/1.8.0-SNAPSHOT/alluxio-core-common-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.8.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.8.0-SNAPSHOT/alluxio-core-common-1.8.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.8.0-SNAPSHOT/alluxio-core-common-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.8.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.8.0-SNAPSHOT/alluxio-core-common-1.8.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.8.0-SNAPSHOT/alluxio-core-server-worker-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.8.0-SNAPSHOT/alluxio-logserver-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.8.0-SNAPSHOT/alluxio-core-client-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.8.0-SNAPSHOT/alluxio-examples-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.8.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.8.0-SNAPSHOT/alluxio-examples-1.8.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.8.0-SNAPSHOT/alluxio-examples-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.8.0-SNAPSHOT/alluxio-core-1.8.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.8.0-SNAPSHOT/alluxio-core-server-proxy-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.8.0-SNAPSHOT/alluxio-shell-1.8.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.8.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.8.0-SNAPSHOT/alluxio-shell-1.8.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.8.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.8.0-SNAPSHOT/alluxio-shell-1.8.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.8.0-SNAPSHOT/alluxio-tests-1.8.0-SNAPSHOT.pomchannel 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/19770/Failed Tests: 32org.alluxio:alluxio-minicluster: 1alluxio.multi.process.MultiProcessClusterTest.zookeeperorg.alluxio:alluxio-tests: 31alluxio.client.fs.FileSystemMasterIntegrationTest.concurrentCreateDeletealluxio.client.fs.FileSystemMasterIntegrationTest.ufsModeReplayalluxio.client.fs.FileSystemMasterIntegrationTest.unavailableUfsRecursiveCreatealluxio.client.fs.FileSystemMasterIntegrationTest.syncDirReplayalluxio.client.fs.FileSystemMasterIntegrationTest.syncReplayalluxio.client.fs.MultiUfsMountIntegrationTest.mountAfterMasterRestartalluxio.server.auth.ClusterInitializationIntegrationTest.recoverClusterFailalluxio.server.auth.ClusterInitializationIntegrationTest.recoverClusterSuccessalluxio.server.ft.MasterFailoverIntegrationTest.failoverJournalFencingTestalluxio.server.ft.ZookeeperFailureIntegrationTest.zkFailurealluxio.server.ft.journal.JournalShutdownIntegrationTest.multiMasterMountUnmountJournalalluxio.server.ft.journal.JournalShutdownIntegrationTest.singleMasterJournalStopIntegrationalluxio.server.ft.journal.JournalShutdownIntegrationTest.singleMasterMountUnmountJournalalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.fileDirectoryalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.deletealluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.addBlockalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.emptyFileSystemalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.directoryalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.renamealluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.setAclalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.persistDirectoryLateralluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.pinalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.filealluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.mountEntryCheckpointalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.completedEditLogDeletionalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.manyFilealluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.multiEditLogalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.loadMetadataalluxio.server.health.StartupConsistencyCheckIntegrationTest.consistentalluxio.server.health.StartupConsistencyCheckIntegrationTest.inconsistentalluxio.server.health.StartupConsistencyCheckIntegrationTest.disabled
Test FAILed.

Jenkins, test 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/19781/Failed Tests: 32org.alluxio:alluxio-minicluster: 1alluxio.multi.process.MultiProcessClusterTest.zookeeperorg.alluxio:alluxio-tests: 31alluxio.client.fs.FileSystemMasterIntegrationTest.concurrentCreateDeletealluxio.client.fs.FileSystemMasterIntegrationTest.ufsModeReplayalluxio.client.fs.FileSystemMasterIntegrationTest.unavailableUfsRecursiveCreatealluxio.client.fs.FileSystemMasterIntegrationTest.syncDirReplayalluxio.client.fs.FileSystemMasterIntegrationTest.syncReplayalluxio.client.fs.MultiUfsMountIntegrationTest.mountAfterMasterRestartalluxio.server.auth.ClusterInitializationIntegrationTest.recoverClusterFailalluxio.server.auth.ClusterInitializationIntegrationTest.recoverClusterSuccessalluxio.server.ft.MasterFailoverIntegrationTest.failoverJournalFencingTestalluxio.server.ft.ZookeeperFailureIntegrationTest.zkFailurealluxio.server.ft.journal.JournalShutdownIntegrationTest.multiMasterMountUnmountJournalalluxio.server.ft.journal.JournalShutdownIntegrationTest.singleMasterJournalStopIntegrationalluxio.server.ft.journal.JournalShutdownIntegrationTest.singleMasterMountUnmountJournalalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.fileDirectoryalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.deletealluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.addBlockalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.emptyFileSystemalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.directoryalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.renamealluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.setAclalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.persistDirectoryLateralluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.pinalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.filealluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.mountEntryCheckpointalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.completedEditLogDeletionalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.manyFilealluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.multiEditLogalluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.loadMetadataalluxio.server.health.StartupConsistencyCheckIntegrationTest.consistentalluxio.server.health.StartupConsistencyCheckIntegrationTest.inconsistentalluxio.server.health.StartupConsistencyCheckIntegrationTest.disabled
Test FAILed.

The failing tests are because this PR relies on [ALLUXIO-3208] masters cannot get id and register.  After merging that PR, the tests should be able to pass.

@LuQQiu can you update this PR?

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/19815/Build result: ABORTED[...truncated 4252 lines...][INFO] Alluxio Integration ................................ SUCCESS [  1.493 s][INFO] Alluxio Integration - Mesos ........................ SUCCESS [  6.933 s][INFO] Alluxio Assembly - Server .......................... SUCCESS [  5.631 s][INFO] Alluxio Integration Checker ........................ SUCCESS [ 28.355 s][INFO] Alluxio Core - Client - HDFS ....................... SUCCESS [ 13.436 s][INFO] Alluxio Core - Client - Runtime .................... SUCCESS [ 11.639 s][INFO] Alluxio Integration - FUSE ......................... SUCCESS [ 11.470 s][INFO] Alluxio MiniCluster ................................ SUCCESS [ 47.499 s][INFO] Alluxio Tests ...................................... FAILURE [  01:44 h][INFO] Alluxio Under File System - GCS .................... SKIPPED[INFO] Alluxio Under File System - HDFS ................... SKIPPED[INFO] Alluxio Under File System - Aliyun OSS ............. SKIPPED[INFO] Alluxio Under File System - S3A .................... SKIPPED[INFO] Alluxio Under File System - Swift .................. SKIPPED[INFO] Alluxio Under File System - Microsoft Azure Blob Storage SKIPPED[INFO] Alluxio Integration - YARN ......................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 01:59 h[INFO] Finished at: 2018-05-24T18:56:30-07:00Archiving artifacts[INFO] Final Memory: 149M/2649M[INFO] ------------------------------------------------------------------------
Test FAILed.

jenkins, test 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/19825/Build result: ABORTED[...truncated 4253 lines...][INFO] Alluxio Log Server ................................. SUCCESS [  5.692 s][INFO] Alluxio Integration ................................ SUCCESS [  1.588 s][INFO] Alluxio Integration - Mesos ........................ SUCCESS [  6.934 s][INFO] Alluxio Assembly - Server .......................... SUCCESS [  6.225 s][INFO] Alluxio Integration Checker ........................ SUCCESS [ 29.117 s][INFO] Alluxio Core - Client - HDFS ....................... SUCCESS [ 14.099 s][INFO] Alluxio Core - Client - Runtime .................... SUCCESS [ 12.548 s][INFO] Alluxio Integration - FUSE ......................... SUCCESS [ 11.082 s][INFO] Alluxio MiniCluster ................................ SUCCESS [ 49.071 s][INFO] Alluxio Tests ...................................... FAILURE [  01:44 h][INFO] Alluxio Under File System - GCS .................... SKIPPED[INFO] Alluxio Under File System - HDFS ................... SKIPPED[INFO] Alluxio Under File System - Aliyun OSS ............. SKIPPED[INFO] Alluxio Under File System - S3A .................... SKIPPED[INFO] Alluxio Under File System - Swift .................. SKIPPED[INFO] Alluxio Under File System - Microsoft Azure Blob Storage SKIPPED[INFO] Alluxio Integration - YARN ......................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 01:59 h[INFO] Finished at: 2018-05-24T23:36:28-07:00[INFO] Final Memory: 141M/2476M[INFO] ------------------------------------------------------------------------
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/19827/Build result: ABORTED[...truncated 4297 lines...][INFO] Alluxio Integration ................................ SUCCESS [  1.688 s][INFO] Alluxio Integration - Mesos ........................ SUCCESS [  6.981 s][INFO] Alluxio Assembly - Server .......................... SUCCESS [  5.569 s][INFO] Alluxio Integration Checker ........................ SUCCESS [ 26.049 s][INFO] Alluxio Core - Client - HDFS ....................... SUCCESS [ 15.221 s][INFO] Alluxio Core - Client - Runtime .................... SUCCESS [ 10.518 s][INFO] Alluxio Integration - FUSE ......................... SUCCESS [ 11.450 s][INFO] Alluxio MiniCluster ................................ SUCCESS [ 51.001 s][INFO] Alluxio Tests ...................................... FAILURE [  01:44 h][INFO] Alluxio Under File System - GCS .................... SKIPPED[INFO] Alluxio Under File System - HDFS ................... SKIPPED[INFO] Alluxio Under File System - Aliyun OSS ............. SKIPPED[INFO] Alluxio Under File System - S3A .................... SKIPPED[INFO] Alluxio Under File System - Swift .................. SKIPPED[INFO] Alluxio Under File System - Microsoft Azure Blob Storage SKIPPED[INFO] Alluxio Integration - YARN ......................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 01:59 h[INFO] Finished at: 2018-05-25T08:56:34-07:00Archiving artifacts[INFO] Final Memory: 139M/2939M[INFO] ------------------------------------------------------------------------
Test FAILed.

Jenkins, test 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/19837/Failed Tests: 0
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/19843/
Test PASSed.

Merged build finished. Test PASSed.

@LuQQiu ready to merge this once conflicts are resolved

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/19846/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.client.fs.ConcurrentFileSystemMasterCreateTest.concurrentListFiles
Test FAILed.

Jenkins, test this please

@LuQQiu  this PR goes to feature branch and the failing test is known to be flaky. Thus I am fine to merge it now


support pagination

need to support pagination on calls that may have more data in a response than a single response can deliver.

for now this is done and working for compartments and instances. will open another one if things are added and pagination is ignored.


Log refactor

What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Think about this pattern ...
pkg/log/constants.go
const RepoNotFoundMsg = "repo not found"
log.Info().Msg(RepoNotFoundMsg)

Error msgs ... to be standardized.
"Failed to ..."
"Error happened ..."
"Unable to ..."

Add a log linter if possible.


DNB: Shifting compacting SRAM FIFOs

Introducing SramDispatchQueueCompactingShifting. FIFO dispatch with multiple dequeue and enqueue and compacting head and tail.
Tested and verified with riscv-test ISA+micro benchmark

@davidmetz
This is the final PR, containing both the other two.


allow modular scripts config

browserify allows you to build 'modules'.  these modules then could contain a number of common libraries and is compiled as a single file.
when another module then requires one of these libraries, you can tell browserify that this file is available externally (i.e. do not include that code when compiling this module). this allows people to separate a vender.js (which rarely/never changes) from app.js.  Within your site you would then have 2 script files. This allows you to separate out your app.js into smaller files (compiled for specific parts of your app).
It would be good to be able to specify modules via node. We should work out how to expose the the src file name within component.build.scripts() function.  This option should then work for requireJS too.
or we have a rule that says all js files found within bower_components are external to all files apart from vender.js files.
i feel component.config.js would be made too complicated if this enhancement was made available here too. i think the config should be relatively simple. maybe we can add this enhancement to the config later, but for now this will be a node only update.
so i guess the question is, automatic (potentially confusing/hidden) vs explicit (potentially a pain as would need gulp)

something like this needs to be incorporated
maybe the vendor bundle goes in the browserify options
var vendorBundle = [
  {file:'./bower_components/dir/component.js', expose:'component'}, //expose if not commonjs
  'd3'
];

then this needs to be within the browserify wrapper
  var b = browserify();
b.transform('debowerify'); //another cool thing

//mark vendor files as external for the main bundle
  b.external(vendorBundle.map(function (v) {
    if (typeof v === 'string') return v;
    return v.expose;
  }));
b.bundle()

//make vendor
  browserify({
    debug: dev
  })
  .transform('debowerify')
  .require(vendorBundle)
  .bundle()
  .on('error', cb)
  .on('end', cb)
  .pipe(source('vendor.js'))
  .pipe(gulp.dest('./public/js'));

PR #69


Support System Installed Extensions

Description
Add support for extensions installed on the system level
Who's implementing?

[ ] I'm willing to implement this feature myself

The problem
I don't use Ungoogled Chromium all that often, just for sites that have issues with Firefox. I still won't go to any site without uBlock Origin. Manually updating uBlock Origin just about every time I startup Ungoogled Chromium is a, albeit very minor, hassle
Possible solutions
I'm using Debian, which has webext-ublock-origin-chromium in its repositories. While it doesn't get feature updates, it should get security and compatibility updates regularly enough. If Ungoogled Chromium could use extensions installed on the system level, that would make it a bit more convenient for my use case
Alternatives
No response
Additional context
I completely understand if this feature won't be implemented. I don't know how much work would have to be done and it's just for a very minor inconvenience for a niche use-case. Thank you for your time!

Interesting concept actually. This may be a viable alternative to "Chromium Web Store" extension.

Interesting concept actually. This may be a viable alternative to "Chromium Web Store" extension.

On top of that, it may be an interesting way to install the "Chromium Web Store" extension for all users on a system.


WASM To Do's

In no real order of priority:

[ ] Use best practice/tips dev tools & optimizations (logging and wee_alloc)
[x] Implement a basic UI for entering expressions and seeing the results
[x] Evaluate a few editors to use for text input

[ ] Fix syntax highlighting bug
[ ] More sensible error messaging

[ ] Fix syntax highlighting bug
[ ] More sensible error messaging


Run conda activate (and source activate if that fails)

If you test by cloning, checking out 41-conda-activate and using cookiecutter path/to/repo

No problems for me, worked fine!


Problems with visibility of .Rmd files after header

I tried to publish a post as .Rmd file with a YAML front matter. Everything works fine until a header appears (e.g.  ## My Title). Header and all the text thereafter appears with an extreme light gray, so that one even almost can't read the text.
But there is no problem with the exact same file using .Rmarkdown file ending instead of a.Rmd ending. .Rmarkdown is rendered by Blackfriday whereas .Rmd is rendered by Pandoc. There are slight differences, but there shouldn't be any different with standard Markdown. I tested .Rmd- files with other Hugo themes and had no problems.
I tried it also with a fresh installation out of the box so that I could prevent an issue of some changes I already had made to the template. What could be the problem?

Having the same issue. Graphs appear in very light colors so unreadable.
Is there a way to have just a white background?

I have used only .md before, but sounds like Pandoc vs Blackfriday does different html output (structure, classes), which does not play correctly with CSS inside theme.
Could you do more investigation what's missing to even out styles between those?

Frankly, I am not an expert in CSS but I believe the problem has to do with static/mermaid/mermaid.css.  If you delete the following code line opacity: 0.2; or set opacity: 1; header in .Rmd files will work again.
/** Section styling */
.section {
  stroke: none;
  opacity: 0.2;
}

The same code segment can be found inmermaid.forest.css  and mermaid.ark.csstoo.  I do not know if there are some side effects but the sample page mermaid.md seems to work well.
If one does not want to do this change one still has the option to use html-codes for headers in .Rmd files, but then one will lose some features of Pandoc like implicit_header_references.

I still have the same problem. I think it is related with the loading order of theme.css and mermaid.css. The new changes in theme.css is overwrote by mermaid.css. It seems need to this line from script.html into header.html. Not sure this change will cause any side effects to others
"<link href="{{"mermaid/mermaid.css" | relURL}}" type="text/css" rel="stylesheet"/>"


feat(User Management): add service to project

PR summary
This PR adds the User Management service to the project/
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@mahakAg This PR contains the new service.

:tada: This PR is included in version 0.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fix(cli): invalid type error when missing exclude flag

This PR resolves an error caused by parsing workspace configuration and merging it with user-provided CLI arguments/flags. Users had to explicitly add the exclude flag or provide it's value in the licensarc.json file, which is ultimately undesirable.
Now, users are not required to explicitly provide this flag nor add it to the licensarc.json file.
Closes #66

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

ℹ Additional Information

Codecov Report
Attention: Patch coverage is 0% with 8 lines in your changes are missing coverage. Please review.

Project coverage is 70.4%. Comparing base (a44e8d3) to head (ff05a37).

Files
Patch %
Lines

src/config.rs
0.0%
7 Missing :warning:

src/commands/verify.rs
0.0%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##            main     #69     +/-   ##
=======================================
+ Coverage   70.3%   70.4%   +0.1%
=======================================
  Files         25      25
  Lines       2760    2777     +17
=======================================
+ Hits        1941    1956     +15
- Misses       819     821      +2

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


Integrate SDK RPC Server and Admin RPC Server to Single RPC Server

What this PR does / why we need it:
Integrate SDK RPC server and Admin RPC server to single RPC server.
There are two reasons for this changes:

To make both SDK and admin RPC route to same server, and process same data on the same server.
To simplify API url and provide unified url on both SDK and admin APIs.

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Because API url will be unified to https://api.yorkie.dev for both SDK and admin,
it will affect all other repositories that uses both SDK and admin API for their service (eg: dashboard).

Additional documentation:

Checklist:

[x] Added relevant tests or not required
[x] Didn't break anything

@krapie We should replace the remaining 11103 port.
https://github.com/search?q=repo%3Ayorkie-team%2Fyorkie+11103&type=code

@krapie It would be better to deploy all after merging the tasks that combine the Admin and SDK ports.


Issues with top level index.html file

@DrDrij is this a theme issue or do I need to dig into jupinx?

@mmcky Yeah I think jupinx will need a look at. Not generating nested lists correctly. Should be something like:

		Introduction to Python

				About Python

				Setting up Your Python Environment

				An Introductory Example

				Python Essentials

				OOP I: Introduction to Object Oriented Programming

		The Scientific Libraries

				NumPy

				Matplotlib

...

the issue was incorrect spacing after a raw directive being applied. This has been fixed in https://github.com/QuantEcon/sphinxcontrib-jupyter/pull/128


Question：Failed to login

May I ask :
In code ：api.pool.add_account(“user1”, “pass1”<EMAIL_ADDRESS><EMAIL_ADDRESS>“mail_pass1”)
user1 is the Twitter username (starts with @),
pass1 is the Twitter password,
<EMAIL_ADDRESS>and mail_pass1 are the gmail email and password associated with Twitter.
Why can't I log in, it says “Failed to login...” .”.
Thanks in advance.

@Eastup123 hi. Probably it should be some extra message with explanation.
There can be many reasons: wrong login/password from X, wrong login/password from mail, mail doesn't support imap or it is turned off, account is blocked in Twitter or there is OTP.
Provide more logs

The account passwords for both X and its mailbox are correct and can be logged in normally, and X works fine, but the following error is still reported. It is not clear why.


WIP: Add EventSource to Implementation to System.Private.CoreLib

Move the source code for EventSource to System.Private.CoreLib so that it can be used within System.Private.CoreLib.
Currently, WIP.  Will continue clean-up before merge.

@brianrob,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@alexperovich note this is incoming to shared. (yay)

@jkotas, I think I've addressed all of your feedback.  I'll have a few more changes to make after this, but wanted to get another read on the CI.

This had some changes that were needed on the TFS side, so I've checked this into TFS.  It should end up here via the mirror.


MongoDB proccess killed by plugin

Description
When plugin get interfaced with MongoDB local server under Windows, MongoDB process will be killed!
P.S. I don't have any other databases on MongoDB server yet, only LuckPerms uses it for now. I also run 2 servers in bungee network, plugin configs are identical!
me.lucko.luckperms.lib.mongodb.MongoSocketOpenException: Exception opening socket
        at me.lucko.luckperms.lib.mongodb.internal.connection.SocketStream.open(SocketStream.java:70) ~[?:?]
        at me.lucko.luckperms.lib.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:128) ~[?:?]
        at me.lucko.luckperms.lib.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:131) ~[?:?]
        at java.lang.Thread.run(Thread.java:833) ~[?:?]
Caused by: java.net.ConnectException: Connection refused: no further information
        at sun.nio.ch.Net.pollConnect(Native Method) ~[?:?]
        at sun.nio.ch.Net.pollConnectNow(Net.java:672) ~[?:?]
        at sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:542) ~[?:?]
        at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597) ~[?:?]
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) ~[?:?]
        at java.net.Socket.connect(Socket.java:633) ~[?:?]
        at me.lucko.luckperms.lib.mongodb.internal.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:64) ~[?:?]
        at me.lucko.luckperms.lib.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:79) ~[?:?]
        at me.lucko.luckperms.lib.mongodb.internal.connection.SocketStream.open(SocketStream.java:65) ~[?:?]
        ... 3 more```

### Reproduction Steps

1. You have licensed minecraft server
2. Enable MongoDB in settings and connect to local server (without credential)
2. Join server
3. Exit server
4. Wait approx. 1 min
5. Check windows processes

As result, `mongod.exe` process will be killed

### Expected Behaviour

Process will not be killed by plugin

### Server Details

GIT #108 Paper 1.18.1

### LuckPerms Version

v5.3.89

### Logs and Configs

Plugin config are identical on 2 servers:
https://gist.github.com/ITeMbI4/a92bd77a6343bb333e2daaf746af90f7

Server logs:
https://gist.github.com/ITeMbI4/8b0af9f150447d8b5d908a28076762cc

### Extra Details

_No response_

Also get this error when server starts
java.lang.IllegalStateException: Can't find a supported sql storage implementation
        at me.lucko.luckperms.common.messaging.MessagingFactory$SqlMessengerProvider.obtain(MessagingFactory.java:201) ~[?:?]
        at me.lucko.luckperms.common.messaging.LuckPermsMessagingService.<init>(LuckPermsMessagingService.java:71) ~[?:?]
        at me.lucko.luckperms.common.messaging.MessagingFactory.getServiceFor(MessagingFactory.java:121) ~[?:?]
        at me.lucko.luckperms.bukkit.messaging.BukkitMessagingFactory.getServiceFor(BukkitMessagingFactory.java:64) ~[?:?]
        at me.lucko.luckperms.common.messaging.MessagingFactory.getInstance(MessagingFactory.java:89) ~[?:?]
        at me.lucko.luckperms.common.plugin.AbstractLuckPermsPlugin.enable(AbstractLuckPermsPlugin.java:167) ~[?:?]
        at me.lucko.luckperms.bukkit.LPBukkitBootstrap.onEnable(LPBukkitBootstrap.java:175) ~[?:?]
        at me.lucko.luckperms.bukkit.loader.BukkitLoaderPlugin.onEnable(BukkitLoaderPlugin.java:51) ~[LuckPerms-Bukkit-5.3.89.jar:?]
        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:264) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
        at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:370) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:500) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
        at org.bukkit.craftbukkit.v1_18_R1.CraftServer.enablePlugin(CraftServer.java:564) ~[paper-1.18.1.jar:git-Paper-108]
        at org.bukkit.craftbukkit.v1_18_R1.CraftServer.enablePlugins(CraftServer.java:478) ~[paper-1.18.1.jar:git-Paper-108]
        at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:286) ~[paper-1.18.1.jar:git-Paper-108]
        at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1202) ~[paper-1.18.1.jar:git-Paper-108]
        at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:317) ~[paper-1.18.1.jar:git-Paper-108]
        at java.lang.Thread.run(Thread.java:833) ~[?:?]
[01:10:24 WARN]: [LuckPerms] Messaging service 'sql' not recognised.```

Hi @ITeMbI4
The [LuckPerms] Exception occurred whilst enabling SQL messaging service error is caused by having the messaging-service setting in the config.yml set to sql when you're not using an sql based storage-method, which MongoDB is not. Also, are you actually adding the connection uri into the config as well? Or only changing the storage-method setting?

Hi, @OmegaWeaponDev
When I have written this bug, I was using storage-method and filled up standard connection without URL.
Yesterday I found URL setting and set it up as well. Now I don't see any errors but not sure in that...

@ITeMbI4
Is this still an issue or have you resolves the errors now?

@ITeMbI4
Is this still an issue or have you resolves the errors now?

I don't get any errors now, thanks for help.


Please re-open Issue #118 - budget printing

Hi! I'm back from vacation. I've upgrade to 0.3.9 within Firefox 44.0.2. The budget still doesn't print correctly. Page 1: blank, Page 2: a lot of white space, No additional pages to print the rest of the budget.
I coun't re-open #118, so created a new issue.

Hey @topcat39, sorry for the confusion, but the changes @falkencreative made will get released as part of 0.4.0. I'll keep releasing 0.3.X releases on FF only until we pass review, not adding any features to that until we get through, which is what resulted in 0.3.9.
So, long story short, it's not out yet. :-)

@topcat39, is this any better for you now? 0.4.1 is out on Firefox and Chrome.

I don't believe it's better -- I've been able to see Firefox printing issues, and I need to take another look at that. I'm not sure why/how Firefox is handling printing in this way, but I'll try to get to the bottom of it the next time I work on the toolkit code.

I still have the same issue.
On Thu, Feb 25, 2016 at 7:29 AM, Kevin Brown<EMAIL_ADDRESS>wrote:

@topcat39 https://github.com/topcat39, is this any better for you now?
0.4.1 is out on Firefox and Chrome.
—
Reply to this email directly or view it on GitHub
https://github.com/blargity/toolkit-for-ynab/issues/230#issuecomment-188762438
.

Firefox fixes have been added, and a pull request in place so the changes can be officially included in a future release. I'll wait to officially close this issue out until the next version of the Toolkit is released.

Hey @falkencreative / anyone else, was this fixed in 0.4.3?

Yes, this should have been fixed in the latest round of changes to this feature. As far as I know, Firefox should be printing correctly now.

I've tested this on Firefox 45.0.1 and it prints correctly. I just need to remember to a) choose portrait orientation and b) have all my categories expanded.

@topcat39 - Just to double check... Are you choosing Portrait just because that's what you prefer? Or selecting Portrait since you have issues with Landscape? I believe landscape should print correctly, but it will waste some space.

@falkencreative Sorry, I should have been more detailed. Yes, Landscape works, but a waste of paper, as you say. The reminders were more for me since I will forget to expand the categories before printing.

@topcat39 Got it. OK, great.
@blargity Looks like this bug can be closed.

@blargity - Quick reminder -- this issue can be closed.

Thank you!


feat: Storage RPC

Motivation
Consumers of hubs may want to know how much storage is allocated per fid so as to reflect that similarly in content being replicated, or to display a warning within a client about approaching limits.
Change Summary
Adds a new RPC endpoint to return the current limits for a given fid.
Merge Checklist
Choose all relevant options below by adding an x now or at any time before submitting for review

[x] PR title adheres to the conventional commits standard
[x] PR has a changeset
[x] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
[x] PR includes documentation if necessary.
[x] All commits have been signed

Additional Context
If this is a relatively large or complex change, provide more details here that will help reviewers

PR-Codex overview
Detailed summary

Added storage limits RPC
Added StorageLimitsResponse message to request_response.proto
Added GetCurrentStorageLimitsByFid RPC to rpc.proto
Updated castStore.ts, userDataStore.ts, verificationStore.ts, signerStore.ts, linkStore.ts, reactionStore.ts, engine.ts, server.ts, storageEventStore.ts to use new storage limits logic

The following files were skipped due to too many changes: packages/hub-web/src/generated/rpc.ts, packages/hub-web/src/generated/request_response.ts, packages/hub-nodejs/src/generated/request_response.ts, packages/core/src/protobufs/generated/request_response.ts, protobufs/docs/rpc.md, apps/hubble/src/storage/stores/storageEventStore.test.ts

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Rebased version here https://github.com/farcasterxyz/hub-monorepo/pull/1211, closing this one.


Awarding bounty should refuse if proposal has no bounty

with a nice message

or if proposal doesn't exist

not relevant


Please update document. File not Found

pip install http://goandroid.qiniucdn.com/opencv_python-2.4.12-cp27-none-win_amd64.whl
File not Found. I suggest you should change language to english

Thanks for report this issue, the cdn provider got something wrong, fixed by change another download domain.
BTW: It is surprised me that there is some noticed this repo and make an issue. I'll think about change language to english if I got more time to do it.


Release Alpha

Codecov Report
Base: 82.81% // Head: 82.64% // Decreases project coverage by -0.16% :warning:

Coverage data is based on head (6c939dc) compared to base (95843f6).
Patch coverage: 64.70% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##            alpha     #151      +/-   ##
==========================================
- Coverage   82.81%   82.64%   -0.17%
==========================================
  Files          27       27
  Lines        2322     2334      +12
==========================================
+ Hits         1923     1929       +6
- Misses        285      289       +4
- Partials      114      116       +2

Impacted Files
Coverage Δ

driver/types.go
0.00% <ø> (ø)

search/request.go
86.36% <ø> (ø)

tigris/collection.go
72.16% <62.50%> (-0.86%)
:arrow_down:

driver/http.go
77.37% <66.66%> (-0.24%)
:arrow_down:

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.


When a MQTTv311 client tries to publish with qos2, and fails OnACLCheck, the client hangs forever and the connection stays open. Should we disconnect the client instead?

http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718042

If a Server implementation does not authorize a PUBLISH to be performed by a Client; it has no way of informing that Client. It MUST either make a positive acknowledgement, according to the normal QoS rules, or close the Network Connection [MQTT-3.3.5-2].

I encountered this when testing my implementation and testing a publish qos2 which succesfully Connects (authenticates), but fails OnACLCheck, in my case using Python Paho client 3.1.1, the publish fails but the client hangs forever on the publish.
When I looked into the broker code it appears on failure of ACL check that it returns nil with no handling.
Please let me know if I am missing anything or misinformed!

This case is the same using client of MQTTv5 too

I believe you are correct @SimonMacIntyre, this is a bug, at least for MQTTv3. If I remember, for v5 there is no provision to disconnect on ACL errors as some servers may wish to obscure their restrictions. I may be wrong though.

I'll take a quick peek! I see these in the v5 spec:

The Client or Server sending the PUBACK packet MUST use one of the PUBACK Reason Codes [MQTT-3.4.2-1]
The Client or Server sending the PUBREC packet MUST use one of the PUBREC Reason Code values. [MQTT-3.5.2-1]

Same  PUBACK reason code for both would be:

135 | 0x87 | Not authorized | The PUBLISH is not authorized.

For qos0, it appears to be handled correctly!

So from reading that it seems like the spec for v3.1.1 should be to either ack and not publish or disconnect. A disconnect seems like the preferred solution as it makes it obvious there is a breach in the server rules; however, I can absolutely imagine a world in which a user of the server may not have control over some functionality of their MQTT client because it may be third part and a disconnection may make the server useless to them. Perhaps a capability could be in order to adjust functionality but that may just add unwanted complexity

Personally I lean towards the disconnect, over the ack and not publish.
I do like the idea of in the future making that configurable in the file configuration, but maybe the disconnect is a reasonable path forward for now and if it becomes a problem for users we can explore making the server configurable on how to handle that only for v3.1.1?

Created a PR #291 to address this.
The server will:

QOS 0
QOS 1
QOS 2

MQTT v3
Ignore
Disconnect
Disconnect

MQTT v3.1.1
Ignore
Disconnect
Disconnect

MQTT v5
Ignore
Puback NotAuthorized
Pubrec NotAuthorized

This has been fixed and released in v2.4.0. Thank you @thedevop!


Does the service work?

I've tried the example URL (https://tokei.rs/b1/github/XAMPPRocky/tokei_rs) from a couple of different ISPs but always get an error like:
Error 502 Ray ID: 542bb9b6bc1fd932 • 2019-12-10 02:17:57 UTC
Bad gateway

Hello, yes sorry there was internal service error and should be back up now.


Timeout shutdown.

Summary:
JIRA issues: MARATHON-8592
Co-authored-by: Nikita Melkozerov<EMAIL_ADDRESS>

@timcharper we still need to know why the crash is called twice from the leader election service.

Ping @timcharper

Ping @timcharper once more.


Get our heroku deployment to integrate with webmaker

Super thimble isn't playing nice with the rest of webmaker staging. In particular, we get a 403 error whenever /verify is hit on the super-thimble domain. This is a login.wm.o error.

Integration with heroku's login server now works.

Nice.

At this point, publishing is broken and I'm following up with a couple of the core webmaker engineers to get the proper credentials to fix this.

FYI, I've filed a bug upstream in Thimble to figure out full deployment, too:
https://github.com/mozilla/thimble.webmaker.org/issues/474

Fantastic. We've hit a wall on this, since I'd need a dedicated domain to make make-valet work on heroku. Cuz reasons haha

Blocked on @jbuck getting a heroku deployment working with Webmaker's staging suite

Closed with https://github.com/mozilla/thimble.webmaker.org/issues/474


there is no "logging" function in ios version.

any plan for ble packets data  saving?

in released app. like  Android version.


LUCENE-10050 Remove DrillSideways#search(DrillDownQuery,Collector) in favor of DrillSideways#search(DrillDownQuery,CollectorManager)

Description
I've deprecated the old API and edited the function javadocs. Feature code in DrillSideways now only relies on using CollectorManagers and calls either searchSequentially or searchConcurrently based on whether or not the executor is supplied. Tests now only use the DrillSideways#search(DrillDownQuery,CollectorManager) functionality.
Tests
DrillSideways already has randomized tests. I edited/removed tests that were using the now deprecated search(Query,CollectorManager) API
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Lucene maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[ ] I have added tests for my changes.

Thanks for tackling this @gautamworah96! I'm hoping to dig into this PR tomorrow. Just letting you know I saw it and am planning to have a look. Thanks again!


E2E: Fix configuration for spot instances on AWS

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
What type of PR is this?

/kind failing-test
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

NONE

Documentation:

NONE

/lgtm


german translation

Brief Information
This pull request is in the type of:

[ ] bug fixing
[ ] new feature
[x] others

What does this PR do?
Added German translation for the project.

Hello, as this PR is approved, why it is still blocked for merge? Anything I missed?

Because it's not approved by someone who has write access for this project, also, could you change base branch to next？

Because it's not approved by someone who has write access for this project, also, could you change base branch to next？

Lots of conflicts on these branch. Should I better close this PR and rebase to next before?

Yes, you can close this one and make a new PR for next


ENH use pynvml to check conda info

I got several issues on platforms where I have a GPU but no access to nvcc, as solvers such as cuml relies on the fact that we can find a nvcc.
I propose to use pynvml to check the GPU info: this will be more robust and this will also allow to access to the name of the GPU, which is more informative (knowing if we have a V100 or a Titan).

I agree (and can look at it now ?) with that !
Also I found out the hard way nvcc can have slightly different versions in different conda envs leading to reinstalls for cuml depending on the -e flag

Would an access not to nvcc but to nvidia-smi would be okay?
(Technically pynvml only mimics the output of nvidia-smi....)

Why not but I think it is easier to user pynvml as it has a python interface no?

I can do what pynvml do in Python using 2 lines: subprocess+ regex.
Also pynvml doesn't give the cuda version... Subprocess+regex can


older jwt dependency blocking aptible-cli install

I have a dependency mismatch because of the out-of-date jwt dependency:
Bundler could not find compatible versions for gem "jwt":
  In Gemfile:
    omniauth-snowflake (>= 0) ruby depends on
      omniauth-oauth2 (~> 1.2) ruby depends on
        oauth2 (~> 1.0) ruby depends on
          jwt (~> 1.0) ruby

    aptible-cli (>= 0) ruby depends on
      aptible-api (>= 0.5.3) ruby depends on
        aptible-resource (>= 0.2.1) ruby depends on
          fridge (>= 0) ruby depends on
            jwt (0.1.13)

Are you okay w/ bumping that up?
Thanks!,
Eliot

Hey @eliotk, sorry — didn't see this issue until now. I'm pushing this to the top of our Ready list. I think it's a duplicate of aptible/aptible-cli#77. In the meantime, I recommend installing aptible-toolbelt globally, and running aptible outside your Bundler context, but I figure you've already done this.

Hi @fancyremarker, we're running into this issue, too. Unfortunately we can't use aptible-toolbelt globally, because we use aptible-cli in our application.
Currently the only way to move forward with Twilio integration is to use the previous major release twilio-ruby of >= 3.0 (latest is 4.11.1).

Update: the Twilio API no longer supports the older gem version, so this is blocking our use of Twilio entirely. We'll have to use another SMS gateway such as Plivo.


Ingress and Route generation refactor.

@ro14nd @rohanKanojia Do we want the IngressEnricher to be included in the default profile for the default yaml manifests generation, like Route for OpenShift?
Or should there be a flag/mojo parameter for eg., enableIngress , expose = true to enable invokation of RouteEnricher and IngressEnricher ?
In simpler words, do we want Ingress.yaml to be generated by default for Kubernetes runtime mode?
@manusa

https://github.com/fabric8io/fabric8-maven-plugin/issues/1374

We need to deduce a logic for finding/detecting kubernetes-controllers inside the cluster, as they are not a namespaced resource. In minikube, the default nginx-ingress-controller deployment is in the kube-system namespace but is it a globally followed arrangement?