RYA-324, RYA-272 Geo refactoring and examples

Description
Refactored geo libraries into separate projects, added examples.
Geo libraries are optional and turned off by default because the GeoTools is has an incompatible license.
Further, geoWave and geoMesa depend on different versions of the GeoTools, so they must be in separate projects.
The new modules (projects) are
geo.common
geo.mongo
geo.geomesa
geo.geowave
These are modules of the project rya.geoindexing
Tests
Existing tests and new examples.
Links
Jira
Checklist

[ ] Code Review
[ ] Squash Commits

People To Reivew
@isper3at

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/276/

this fixes RYA-324 and RYA-272

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/278/Build result: ABORTED[...truncated 6.55 MB...][INFO] [INFO] --- maven-jar-plugin:2.5:jar (default-jar) @ rya.pcj.fluo.demo ---[INFO] Building jar: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.pcj.fluo/pcj.fluo.demo/target/rya.pcj.fluo.demo-3.2.11-incubating-SNAPSHOT.jar[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 14 iota=59[INFO] [INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ rya.pcj.fluo.demo ---[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 14 iota=59[INFO] [INFO] --- maven-source-plugin:2.4:jar-no-fork (attach-sources) @ rya.pcj.fluo.demo ---[INFO] Building jar: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.pcj.fluo/pcj.fluo.demo/target/rya.pcj.fluo.demo-3.2.11-incubating-SNAPSHOT-sources.jar[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 14 iota=59[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: Invalid object ID 14 iota=59[INFO] [INFO] --- maven-jar-plugin:2.5:test-jar (default) @ rya.pcj.fluo.demo ---[INFO] Building jar: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.pcj.fluo/pcj.fluo.demo/target/rya.pcj.fluo.demo-3.2.11-incubating-SNAPSHOT-tests.jar[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 14 iota=59[INFO] [INFO] --- maven-assembly-plugin:2.4.1:single (make-assembly) @ rya.pcj.fluo.demo ---Adding org.apache.maven.scm.provider.ScmProvidersvnBuild was abortedchannel stoppedSetting status of bc80340c55806317c2336dbde7032c8a476c235d to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/278/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

asfbot build

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/280/Build result: FAILURE[...truncated 8.67 MB...][INFO] Apache Rya Spark Support ........................... SKIPPED[INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 44:49 min[INFO] Finished at: 2017-07-26T15:55:19+00:00[INFO] Final Memory: 212M/1136M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (check-licenses) on project rya.geowave: Too many files with unapproved license: 1 See RAT report in: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.geowave/target/rat.txt -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :rya.geowavechannel stoppedSetting status of bc80340c55806317c2336dbde7032c8a476c235d to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/280/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

In general, this looks ok -- I agree with Andrew's comments but I'm not sure that that should hold up merging this pr -- introducing a factory could be done as a follow on task if it is documented in jira.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/328/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/330/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/324/Build result: ABORTED[...truncated 6.65 MB...][INFO]                                                                         [INFO] ------------------------------------------------------------------------[INFO] Building Apache Rya PCJ Fluo Demo 3.2.11-incubating-SNAPSHOT[INFO] ------------------------------------------------------------------------[INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ rya.pcj.fluo.demo ---[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 14 iota=59[INFO] [INFO] --- apache-rat-plugin:0.11:check (check-licenses) @ rya.pcj.fluo.demo ---[INFO] 51 implicit excludes (use -debug for more details).[INFO] Exclude: /resources/META-INF/services/[INFO] 4 resources included (use -debug for more details)[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 4 licence.[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 14 iota=59[INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-mvn) @ rya.pcj.fluo.demo ---Build was aborted[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 14 iota=59[INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ rya.pcj.fluo.demo ---channel stoppedSetting status of<PHONE_NUMBER>41b0e0d7aa10f3b95cf9b7691376dc to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/324/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

I know that we planned to commit this PR to master first, but #186 is ready to go.
I looked at this and #186.  It turns out that we can commit #186 into master, then commit this PR, and we won't have any merge issues.  Since #186 is ready now, I'm going to commit it, and then assist you with any issues you have merging this PR.
--Aaron

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/333/Build result: FAILURE[...truncated 6.96 MB...][INFO] Total time: 44:09 min[INFO] Finished at: 2017-08-02T15:51:54+00:00[INFO] Final Memory: 250M/3314M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project rya.geoCommon: Compilation failure[ERROR] /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.common/src/main/java/org/apache/rya/indexing/accumulo/geo/OptionalConfigUtils.java:[86,33] method getStrings in class org.apache.hadoop.conf.Configuration cannot be applied to given types;[ERROR] required: java.lang.String,java.lang.String[][ERROR] found: java.lang.String,org.apache.rya.indexing.GeoIndexerType[ERROR] reason: varargs mismatch; org.apache.rya.indexing.GeoIndexerType cannot be converted to java.lang.String[ERROR] -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :rya.geoCommonchannel stoppedSetting status of 881f2589a85181901b9a9b539a32e8c68b303d05 to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/333/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/337/Build result: FAILURE[...truncated 6.96 MB...][INFO] Apache Rya Spark Support ........................... SKIPPED[INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 29:14 min[INFO] Finished at: 2017-08-02T20:55:43+00:00[INFO] Final Memory: 256M/3207M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (check-licenses) on project rya.geowave: Too many files with unapproved license: 1 See RAT report in<EMAIL_ADDRESS>-> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :rya.geowavechannel stoppedSetting status of 2df0d571133eea02a9597bbf7caa6cc99c577e2e to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/337/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/336/Build result: FAILURE[...truncated 7.42 MB...][INFO] Apache Rya Spark Support ........................... SKIPPED[INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 58:50 min[INFO] Finished at: 2017-08-02T21:00:40+00:00[INFO] Final Memory: 281M/2629M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (check-licenses) on project rya.geowave: Too many files with unapproved license: 1 See RAT report in: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.geowave/target/rat.txt -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :rya.geowavechannel stoppedSetting status of 6a94e7b59bd4b6d29e9df74f60c1a31493421862 to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/336/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/338/Build result: FAILURE[...truncated 7.10 MB...][INFO] Apache Rya Spark Support ........................... SKIPPED[INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 29:52 min[INFO] Finished at: 2017-08-02T21:56:49+00:00[INFO] Final Memory: 499M/3383M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (check-licenses) on project geo.geowave: Too many files with unapproved license: 1 See RAT report in: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.geowave/target/rat.txt -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :geo.geowavechannel stoppedSetting status of ccc4fea642df499e9f0476277abc686ee797dbd3 to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/338/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Nit on artifact names.  Please make them consistent with other artifacts:
[INFO] Reactor Build Order:
[INFO]
[INFO] Apache Rya Project
[INFO] Apache Rya Common Projects
[INFO] Apache Rya Common API
[INFO] Apache Rya Provenance
[INFO] Apache Rya DAO Projects
[INFO] Apache Rya Accumulo DAO
[INFO] Apache Rya MongoDB DAO
[INFO] Apache Rya Extra Projects
[INFO] Apache Rya Prospector
[INFO] Apache Rya Manual
[INFO] Apache Rya SAIL
[INFO] Apache Rya PCJ Core
[INFO] Apache Rya PCJ Fluo Parent
[INFO] Apache Rya PCJ Fluo App
[INFO] Apache Rya PCJ Fluo API
[INFO] Apache Rya Secondary Indexing
[INFO] Apache Rya Console
[INFO] Apache Rya Secondary Indexing Example
[INFO] Apache Rya MapReduce Tools
[INFO] Apache Rya Reasoning
[INFO] Apache Rya Vagrant VM
[INFO] Apache Rya PCJ Fluo Client
[INFO] Apache Rya PCJ Fluo Integration Tests
[INFO] Apache Rya PCJ Fluo Demo
[INFO] Apache Rya Export Parent
[INFO] Apache Rya Export API
[INFO] Apache Rya Export Accumulo
[INFO] Apache Rya Export Mongo
[INFO] Apache Rya Export Client
[INFO] Apache Rya Export Integration Tests
[INFO] Apache Rya Merge Tool
[INFO] Apache Rya Giraph
[INFO] Apache Rya Benchmarks
[INFO] Geo indexing parent for multiple geo implementations
[INFO] Apache Rya Geospatial Secondary Indexing (Optional)
[INFO] Geo Indexing using GeoMesa
[INFO] Geo indexing using GeoWave
[INFO] Geo indexing for mongo
[INFO] Apache Rya OSGI Bundle
[INFO] Apache Rya ALX
[INFO] Apache Rya ALX Console
[INFO] Apache Rya Camel
[INFO] Apache Rya Pig Projects
[INFO] Apache Rya Accumulo Pig
[INFO] Apache Rya Spark Support
[INFO] Apache Rya Web Projects
[INFO] Apache Rya Web Implementation

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/346/Build result: FAILURE[...truncated 6.94 MB...][INFO] Apache Rya Spark Support ........................... SKIPPED[INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 28:21 min[INFO] Finished at: 2017-08-03T17:43:07+00:00[INFO] Final Memory: 325M/2928M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (check-licenses) on project geo.geowave: Too many files with unapproved license: 1 See RAT report in: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.geowave/target/rat.txt -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :geo.geowavechannel stoppedSetting status of eecd61458b7b0a2a022b9436bab3ab2210ddab42 to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/346/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/347/Build result: FAILURE[...truncated 6.48 MB...][INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 23:24 min[INFO] Finished at: 2017-08-03T17:59:32+00:00[INFO] Final Memory: 398M/2938M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (check-licenses) on project geo.geowave: Too many files with unapproved license: 1 See RAT report in: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.geowave/target/rat.txt -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :geo.geowavechannel stoppedSetting status of 7b752c5972388be9014b26c1e0c7e0b61ea5c6be to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/347/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

hey @DLotts ?can you fix the merge conflict

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/443/Build result: FAILURE[...truncated 3.21 MB...][INFO] ------------------------------------------------------------------------[INFO] Total time: 25:21 min[INFO] Finished at: 2017-08-24T19:24:17+00:00[INFO] Final Memory: 232M/2942M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project geo.common: Compilation failure: Compilation failure:[ERROR] /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.common/src/main/java/org/apache/rya/indexing/accumulo/geo/GeoTupleSet.java:[52,27] package joptsimple.internal does not exist[ERROR] /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.common/src/main/java/org/apache/rya/indexing/accumulo/geo/GeoTupleSet.java:[152,25] cannot find symbol[ERROR] symbol:   variable Strings[ERROR] location: class org.apache.rya.indexing.accumulo.geo.GeoTupleSet[ERROR] -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :geo.commonchannel stoppedSetting status of beaff5dfd71a14346e7b72696180219009e29532 to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/443/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/449/Build result: FAILURE[...truncated 3.52 MB...][INFO] Apache Rya Spark Support ........................... SKIPPED[INFO] Apache Rya Web Projects ............................ SKIPPED[INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 28:37 min[INFO] Finished at: 2017-08-24T22:02:12+00:00[INFO] Final Memory: 464M/3011M[INFO] ------------------------------------------------------------------------[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (check-licenses) on project geo.geowave: Too many files with unapproved license: 1 See RAT report in: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.geowave/target/rat.txt -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :geo.geowavechannel stoppedSetting status of 651767575de77fb1c7ca11237e3b420f9875ccf8 to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/449/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

asfbot build

hey @DLotts you have a rat failure

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/451/Build result: FAILURE[...truncated 3.60 MB...][INFO] Apache Rya Web Implementation ...................... SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 39:12 min[INFO] Finished at: 2017-08-24T22:57:43+00:00[INFO] Final Memory: 301M/3184M[INFO] ------------------------------------------------------------------------Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (check-licenses) on project geo.geowave: Too many files with unapproved license: 1 See RAT report in: /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/rya.geoindexing/geo.geowave/target/rat.txt -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :geo.geowavechannel stoppedSetting status of 651767575de77fb1c7ca11237e3b420f9875ccf8 to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/451/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/459/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/460/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/461/

Please rename these Maven artifactIds. This helps to avoid artifact name collisions and eases jar identification.
geo.common ==> rya.geo.common
geo.geomesa ==> rya.geo.geomesa
geo.geowave ==> rya.geo.geowave
geo.mongo ==>    rya.geo.mongo
No need to rename anything in the filesystem, just in the poms -- although, you could drop the 'geo.' in the filepath if you really really wanted to.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/463/


v0.2.3-rc2 - OSX: C# plugin not loading

Getting an error on initialize of the omnisharp-server

This is failing both for local build and DMG.

Getting this error message:
"{"jsonrpc":"2.0","id":0,"error":{"code":-32603,"message":"Request initialize failed with message: Cannot read property 'split' of undefined"}}"

Not sure where the split is coming from. At some point, this was working - it seems like it could potentially be an Omnisharp bug, or an issue with the pathing / initialization parameters.

Looks like this is a regression of removing the node dependency - we weren't passing the full set of environment variables, and path was being used by omnisharp-node-client.


% in Positions section shows wrong value in resolved state

To reproduce Short an Outcome  For example short Yes at 0.5) when market gets reported, Make "No" the winning outcome (so your short "Yes" position wins.)
Total returns looks correct, but the realized % is wrong
Last price currently doesnt change....should make that the correct value per outcome:
So If No is the winning outcome, No would show at 1.0 and all other outcomes would show at 0 in last price

when market is awaiting finalization loser positions won't show correct percentage lost.
when market is finalized the percentages will be correct.
when winners claim. loser's frozen funds will reduce, indicating their loss.

this appears fixed


Suggested latex reverse search command is not working

https://github.com/kak-lsp/kak-lsp/blob/7c8c71a90f524a473dceaf08e499b531a7bec4cb/kak-lsp.toml#L233
The command for reverse search (i.e. clicking on your document in pdf viewer to make editor jump to the corresponding source location) that's suggested in the config file now is not working. It gives me this error:
': 2:17: 'evaluate-commands': no such client: 'opt{texlab_client}'
error running command '
                evaluate-commands -client opt{texlab_client} {
                    evaluate-commands -try-client opt{jumpclient} {
                        edit -- {input} {line}
                    }
                }

It seems that something has changed on Kakoune side and we need to update kak-lsp config accordingly. Does anyone know how to modify that command to make reverse search work correctly?
Ivan

works for me with latest master of Kakoune and kak-lsp.
Looks like something is stripping the %, for example it should be %opt{texlab_client}. Maybe your shell does that? What's your kak-lsp.toml? The default one uses sh -c '...'

with the default kak-lsp.toml, ps aux | grep zathura | grep [%]opt should show the running pdf viewer

I'm looking for a way to reproduce.
What's the output of
ps aux | grep -o 'zathura .*' | sed 's/ \+/ /g'

It should be something like
zathura /tmp/test.pdf --synctex-forward 1:1:/tmp/test.tex --synctex-editor-command sh -c ' echo " evaluate-commands -client %opt{texlab_client} %{ evaluate-commands -try-client %opt{jumpclient} %{ edit -- %{input} %{line} } } " | kak -p $kak_session '

if that has % (in %opt{texlab_client}, then the problem could be in $(which sh)
if it doesn't have %, then maybe zathura is at fault
What are your versions of sh, zathura, Kakoune, kak-lsp?
Does it reproduce with the default configuration? (that one will rule out any customization from your $HOME)

Do you have an idea of who could be doing the expansion of %?

Maybe zsh? what's file $(which sh)
Will give more info later.

$ mv .config/kak-lsp/kak-lsp.toml .config/kak-lsp/backup
$ HOME=$(mktemp -d) kak -e '

no need to move the config if you override HOME

$ zathura --version
zathura 0.5.2
girara 0.3.9 (runtime: 0.4.0)
(plugin) pdf-mupdf (0.4.1) (/usr/lib/zathura/libpdf-mupdf.so)


Refactor global-network-policies and control plane network policies into component

How to categorize this PR?

/area dev-productivity quality robustness
/kind technical-debt test
/priority 3
/topology seed
/platform all
/exp intermediate
What this PR does / why we need it:
This PR refactors the deployment for the global and shoot control plane specific network policies. It adopts the component concept. Consequently, it eliminates the Helm chart and adds full unit tests, instead. This improves several aspects and the overall code quality.
Which issue(s) this PR fixes:
Part of #2754
/squash
Release note:

NONE

/assign

@BeckerMax Thanks for the review, I’ve addressed some of the suggestions with b3c2b78804b03ae9acf6d433f1f23314e2122336 and answered to some others. Please take another look :)

/lgtm


Use ccache (optionally) in CMake builds

Hi folks,
Have you considered using ccache to speed up repeat builds on linux and mac machines?  It caches built object files, allowing them to be reused if the underlying source hasn't changed.  For us, this speeds our CI builds dramatically - we're building ChakraCore as a static library, and adopting ccache has taken our build from 30 minutes to one.
I'm proposing adding the following to the root CMakeLists.txt:
if(USE_CCACHE) # set by build.sh
  find_program(CCACHE_PROGRAM ccache)
  if(CCACHE_PROGRAM)
    set(CMAKE_CXX_COMPILER_LAUNCHER ${CCACHE_PROGRAM})
    set(CMAKE_C_COMPILER_LAUNCHER   ${CCACHE_PROGRAM})
  endif()
endif()

Would you be amenable to such a change?

I don't see the issue with making a PR for this, but I also am a bit confused, since I usually don't have rebuild-the-world events in build.sh unless I change a core flag, like --no-icu to --system-icu (which changes some global defines). Could you provide a bit more info on how you are invoking build.sh each time?

Sure.  I'm incorporating ChakraCore as a CMake external project; a fresh build will clone the Chakra repo and build it on the dev's machine.  We do have build-the-world events occasionally, in the process of development.
It's more important for CI, where I definitely would prefer a clean build for each change.

Ah, that makes sense. I think this sounds pretty reasonable, though I don't think we would be able to take advantage of it ourselves since I think our CI runs don't share any state at all. @dilijev thoughts?

You are right, no benefit to our CI, but embedders of ChakraCore may benefit from an improved experience / build times, so I don't see why not.

IMHO we don't need cache. Current build script will rebuild only the files updated ++ you can set the output path as any location. So, re-clone wouldn't break the cache.
See build.sh
``
--target-path[=S] Output path for compiled binaries. Default: out/

The benefit accrues primarily to CI scenarios, where we strongly prefer a clean build each time.  Having a compiler cache means that such changes add maybe 1-5 minutes to the build, rather than 35.

I am unfamiliar with CCache and a quick glance at the website doesn't tell me a whole lot, but what exactly does it do that --target-path doesn't do? SCCache's benefit is more clear, but only useful in the case where the filesystem isn't shared between machines (such as some CI systems, not sure about yours).

ccache is conceptually a hash table; it uses a hash of source-file path, mtime, compiler flags, etc. for each compiled object file.  It sits between the build system and the compiler (hence, CMAKE_CXX_COMPILER_LAUNCHER).  It will hash the compiler arguments, and if there is a matching object file in the cache, will just use that rather than compiling.
In constrast, --target-path just specifies the build output directory.  Make (and any build system, really) will avoid compiling files that haven't changed, if there is a suitably-named object file in the output directory whose mtime is greater than the source file.
ccache maintains its cache elsewhere, so you can delete part (or all) of the --target-path and still have a fast build.  This is why CI benefits so much - builds typically happen in an isolated arena without any shared --target-path; with ccache, you can avoid recompiling things that haven't changed.

+1 to this PR- @obastemur what's the downside of supporting ccache along with --target-path?

I don’t really see how we are going to benefit from that OR use / test that so we know when it breaks

seems like a simple enough feature that 1) it would be difficult to break and 2) even if we did break it at some point somehow, it is still preferable between now and then for embedders who want to use this to not have to fork our build system to accomplish it. Also, if we can get SCCache + Azure to work (which Benjamin has a different PR out for, I noticed), there is a world in which this sounds really great for use in Jenkins, especially if we wanted to keep adding on to our build matrix. For what its worth, is --target-path tested or used by anything right now?

Package creator uses that. ;)
Well, I just brought a concern. Consider me in deferent about this feature.


"Peștera", "Ivrinezu Mare" are listed in the drop-down menu

Description:
When user writes "Peștera", "Ivrinezu Mare"  the location appears in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Ivrinezu Mare"

Expected results
The location appears in the drop-down menu as "Sat Ivrinezu Mare, CONSTANȚA, (Peștera)"


bandeiras

Type: Feature Request
Olá eu gostaria de pedir para adicionarem uma funcionalidade de poder colocar cores nas abas dos arquivos e uma forma de marca com cor de fundo ou com uma bandeira mais poder marcar os arquivos que estou trabalhando ou que desejo me focar mais.
Desde ja agradeço.
Automated translation:
Hello I would like to ask you to add a feature of being able to put colors in the tabs of the files and a branded shape with background color or with a flag more power to mark the files I'm working or that I want to focus more.
 Since I thank you.
VS Code version: Code 1.70.1 (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:08:33.642Z)
OS version: Windows_NT x64 10.0.22000
Modes:

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


toDateString() new operator - Microsoft Official Docs update

Category

[x] Content fix
[ ] New article

Related issues
"Content fix" category selected, given that it's an existing content update and no issues are related to this pull request. Available for clarification and further changes.
What's in this Pull Request?
New toDateString() operator short description, including a basic example. This addition has been implemented by taking the existing content as a writing style reference.

Docs Build status updates of commit a22435d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/declarative-customization/formatting-syntax-reference.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


CodeUnit 5703 - Nonstock Item Management - GetNewItemNo

Hi, would it be possible to change the procedure GetNewItemNo in codeunit 5703 from local to external?
Thanks for your time

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Redactor does not allow you to format bold, italic, underline, sup, sub etc. for selected text

Describe the bug
Redactor does not allow you to format bold, italic, underline, sup, sub etc. for selected text
To Reproduce
Steps to reproduce the behavior:

Go to pages
Click on create new page
Scroll down to the content WYSIWYG
Try and select an individual work and format in bold / italic.

Expected behavior
The selected piece of text should be formatted.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. Windows 10]
Browser: Chrome
Version 68.0.3440.106

Additional context
This is related to the following issue: https://github.com/vova07/yii2-imperavi-widget/issues/89

Yeah I've recently started the update for Redactor 3, I should have it done by this weekend

Any updates on this?

Updated in the latest release

Why is this closed? Just updated to the latest release (v3.1.7) and I can confirm the issue still remains:

Please clear your caches etc and make sure the new version of Redactor loads. The entire toolbar of the editor looks different now.

I've cleared all the cache, cleared composer cache, compiled the assets again and restarted the server. Still no change.

Okay so after running npm run production and clearing the cache again this issue seems to be fixed now. Thanks


On Click of Logout User-device tokens should be deleted from the database for sending notifications smoothly.

Description:
onclick of Logout, users Device Tokens should be  deleted

@Ijaiswalshivam assign me

@hdhimalay assigned


runmodels add --inplace option

Following a hackathon where nrn-modeldb-ci was used, it would be very helpful to re-run a model in place.
We need to be aware of #19 while implementing this.

Since new options have been coming in, also worth refactoring together with this ticket.


[Snyk] Upgrade @sectester/runner from 0.16.5 to 0.29.1

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade @sectester/runner from 0.16.5 to 0.29.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 23 versions ahead of your current version.

The recommended version was released on a month ago.

Release notes

Package name: @sectester/runner

0.29.1 - 2024-06-220.29.1 (2024-06-22)
Bug Fixes

repeater: remove unwanted name-prefix modification (#204) (9c1a1bc), closes #196

0.29.0 - 2024-06-200.29.0 (2024-06-20)
Features

bus: get rid of amqp event bus (#198) (b2809e9), closes #196

0.28.0 - 2024-06-190.28.0 (2024-06-19)
Features

repeater: refrain from utilizing non standard ports (#197) (aa12bfa), closes #196

0.27.0 - 2023-08-030.27.0 (2023-08-03)
Features

scan: add new iframe_injection test type (#177) (3907a86), closes #176

0.26.0 - 2023-07-310.26.0 (2023-07-31)
Features

scan: add new css_injection test type (#175) (d8495a1), closes #174

0.25.0 - 2023-07-280.25.0 (2023-07-28)
Features

scan: add new prompt_injection test type (#173) (1411f2d), closes #172

0.24.1 - 2023-07-200.24.1 (2023-07-20)
Bug Fixes

core: use ISO format in log messages (#171) (6787e6e), closes #164

0.24.0 - 2023-07-200.24.0 (2023-07-20)
Features

scan: add stored_xss and deprecate dom_xss (#170) (96040b5), closes #169

0.23.2 - 2023-06-270.23.2 (2023-06-27)
Bug Fixes

repeater: create RMQConnectionManager in the scope of the child container (#163) (644eb50), closes #162

0.23.1 - 2023-06-190.23.1 (2023-06-19)
Bug Fixes

bus: channel closed error while processing an incoming message (#161) (8e9363d), closes #159

0.23.0 - 2023-06-18

0.22.0 - 2023-06-17

0.21.0 - 2023-06-17

0.20.2 - 2023-06-16

0.20.1 - 2023-06-12

0.20.0 - 2023-06-05

0.19.3 - 2023-06-05

0.19.2 - 2023-06-05

0.19.1 - 2023-05-24

0.19.0 - 2023-05-23

0.18.1 - 2023-05-02

0.18.0 - 2023-03-16

0.17.0 - 2023-02-09

0.16.5 - 2022-10-28

    from @sectester/runner GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Checkmarx One – Scan Summary & Details – b1e58a0b-bb70-4f6d-b2b5-37081197a22d
Fixed Issues

Severity
Issue
Source File / Package

Unpinned Actions Full Length Commit SHA
/release.yml: 37

CVE-2024-39249
Npm-async-2.6.4

CVE-2024-39249
Npm-async-3.2.3

updated to 0.33.1 in #359: https://github.com/NeuraLegion/brokencrystals/blob/c7a46e2150ac80a4ee018c9e3d2bf3ab26ed7cee/package.json#L46


V8.2.2 is not compatible with otel v0.20.0

I would like to use opentelemetry v0.20.0  in my project, my boss ask me that the project must use go-redis v8.2.2, Although it’s a very strange request for me ¯_(ツ)_/¯
After I tested it, there seemed to be some kind of dependency error as flowing as bellow.
Does anyone understand what happened? How do I solve it.
Context (Environment)
go version go1.16.4 darwin/amd64
github.com/go-redis/redis/v8 v8.2.2
go.opentelemetry.io/otel v0.20.0
Detailed Description
go: downloading golang.org/x/sys v0.0.0-20210305230114-8fe3ee5dd75b
go: finding module for package go.opentelemetry.io/otel/api/metric
go: finding module for package go.opentelemetry.io/otel/label
go: finding module for package go.opentelemetry.io/otel/api/trace
go: finding module for package go.opentelemetry.io/otel/api/global
erc/pkg/mytest/service imports
        github.com/go-redis/redis/v8 imports
        go.opentelemetry.io/otel/api/trace: module go.opentelemetry.io/otel@latest found (v0.20.0), but does not contain package go.opentelemetry.io/otel/api/trace
erc/pkg/mytest/service imports
        github.com/go-redis/redis/v8 imports
        go.opentelemetry.io/otel/label: module go.opentelemetry.io/otel@latest found (v0.20.0), but does not contain package go.opentelemetry.io/otel/label
erc/pkg/mytest/service imports
        github.com/go-redis/redis/v8 imports
        github.com/go-redis/redis/v8/internal imports
        go.opentelemetry.io/otel/api/global: module go.opentelemetry.io/otel@latest found (v0.20.0), but does not contain package go.opentelemetry.io/otel/api/global
erc/pkg/mytest/service imports
        github.com/go-redis/redis/v8 imports
        github.com/go-redis/redis/v8/internal imports
        go.opentelemetry.io/otel/api/metric: module go.opentelemetry.io/otel@latest found (v0.20.0), but does not contain package go.opentelemetry.io/otel/api/metric

Many people have encountered the dependency problem of opentelemetry. We have lifted the dependency on opentelemetry in version v8.11.0

For now, upgrading to v8.11.0 does not need to change anything, it is compatible with v8.2.2.

@monkey92t Thank you so much for answering generously.


Fix library for failed test on elixir 1.2.0

Fix #6
For some reason, %ExUnit.state format we received in the function generate_test_body is not correct. We get something like {:failed, [failed]} instead of `{:failed, failed}
I added a new clause for generate_test_body taking care of this new format. I am not entirely sure of the root cause of this problem, but this fix will solve it.

@adrienmo I think this is the new behavior in Elixir 1.2.0:

[ExUnit] Allow one test to raise multiple errors. The goal is to enable tools in the ecosystem to emit multiple failure reports from the same test

We should probably support multiple failures instead of ignoring all but the first one

@andruby This is indeed something introduce in elixir 1.2.0:
https://github.com/elixir-lang/elixir/blob/v1.2.0/lib/ex_unit/lib/ex_unit/runner.ex#L353
But I think in most case, only one element will be present in the array. Multiple will be present if the user specifically raise several errors:
raise ExUnit.MultiError, errors: [error1, error2]

I am not sure how and if it is really useful to merge the different error into one message error for the test case ?

I agree with @adrienmo that we should support all failures from a test. I will merge this one for now because it fixes #6.
Do you guys think that several failure nodes will break Jenkins or other tools that read this XML? I know that in Java you can only have one failed assertion per test but several failure nodes is also valid XML.
@adrienmo @andruby what do you guys think?


Does parse server code include push notifications systems.

Till now, parse has been providing me notifications solutions, but now as it is closing down, i need to migrate to some other solution.
Will setting up a parse server on my own server (VPS or dedicated) solve the issue and would i be able to operate with as simplicity as i used to with parse service and dashboard.
Does parse server code include push notifications system and UI.
Do let me know so it can clear my doubts about the parse server code and its migration capabilities, thank you

Push is coming really soon to parse-server, but it hasn't been implemented already.
It's worth waiting to check it out, and if it's not, take a look at OneSignal, PushWoosh, or other providers.
If it answers your questions, close this issue :smile:

Should be active within 1 week.  Parts of it are being added in currently open pull requests.  Hang in there! :santa:


Master Task Throttling

Is your feature request related to a problem? Please describe.
For many cluster activities, data nodes submits tasks to master node. Like for put-mapping, create-index, shard started, etc. Sometimes due to some bug or issue Data nodes floods the master node with too many tasks, as a result we can see the spikes in pending task in master queue. This can affect master's performance, which can effect availability of whole cluster.
We should increase master's resiliency against such high pending task.
Describe the solution you'd like
We can make master more resilient by adding throttling of tasks on master node. Master will reject task submitted from data node based on throttling limits.  This throttling should work on task type basis, so throttling of one task wont affect different task's submission.
Once master rejects such task based on throttling logic, data node will perform retries exponential back off to submit this tasks to master node.
We should make dynamic setting for enabling and disabling throttling on master and we should also be able to provide throttling configuration for task types in dynamic setting.
This framework will help if there are some bugs/issue in cluster, we can enable throttling for making master resilient against high tasks and disable it when underlying bug/issue gets resolved.
Describe alternatives you've considered
De-duplication of tasks: We have de-duplication framework as well which prevents submitting duplicate tasks to master node, but it wont help for all the cases. Data nodes can submit different tasks and flood master or master gets flooded from customer driven activities as well where tasks wont be duplicate. We want to make master resilient against high pending tasks, so de duplication wont help achieving it.
Additional context
Master performs the batching of tasks, so it iterate over all the task queued in master queue to see whether they can be batched or not, also such tasks will be remain in queue until they are not executed hence it will consume memory as well(memory according to particular task types).
So such high pending tasks on master queue can affect CPU/JVM of master node and can affect the availability of whole cluster.

Breaking changes in multiple PR:

[ ] Add Master task throttling changed in data/master nodes(#553)
[ ] Add Throttling Stats on Stats API
[ ] Add Documentation of new Settings.

Hi @dhwanilpatel, are you actively working on this? could please provide some updates?

There was an attempt in https://github.com/opensearch-project/OpenSearch/pull/553 to implement this that hasn't been finished. Please feel free to pick it up where it was left!

Hello,
I am going to pick this up again to take this changes to completion. Major feedback on last PR (#554) was to break the changes into multiple PRs for ease of review. Below is plan on how I will be breaking changes into multiple PR.

[ ] Basic Throttler Framework / Exponential Basic back off policy.
[ ] Changes required in Master node to perform throttling.
[ ] Changes required in Data node to perform retry on throttling.
[ ] Provide support for all task type in throttling framework.
[ ] Integration Tests

Below are the list of item for future followup checks,

[ ] Documentation regarding new settings.
[ ] Throttling stats in Stats API.

@dblock  can you please help in creating the feature branch for this issue, against which we can raise multiple PRs.

@dhwanilpatel Hey, how's it going?  Can we we help at all?

@CEHENKLE  so far it is going as per plan, Data Node and Master Node side changes are in review state. After those PR, upcoming PRs should be straightforward.
Thanks to the reviewers for providing their valuable feedbacks.

@dhwanilpatel Cool beans.   LMK if we can help :)
/C

@dhwanilpatel need a task in here for integ tests as well.

@dhwanilpatel I wanted to confirm if this is on track for the 2.3 release. If so, pls add the v2.3.0 label to this issue. Thanks!

Created followup SIM for exposing throttling exception to user : https://github.com/opensearch-project/OpenSearch/issues/4724

@dhwanilpatel given we are calling the feature "Cluster Manager Task Throttling" can we rename this issue "Cluster Manager Task Throttling"?


Fix the link to input configuration

Description
This fixes the link to input configuration. The current link leads to a 404 page.

thanks 🎉


Getting Started Instructions

Hello,
I am exploring different frameworks to help incorporate UI decomposition into my project so we can break up a monolithic UI codebase. Compoxure looks interesting to me, but I am not sure how to actually start getting it all set up for my own project. I understand the configuration file documentation, but what is needed to start using this tool for my own app?
Looking at the example code, it seems like I have to write my own version of proxy.js. Would that be correct?
I know I have a lot of questions here, but it would be good to have some "Getting Started" documentation to help direct new developers looking to adopt this project.

Correct - you need to create a simple express app that you add the middleware in this project to, and pass in the config to.  The version in example/proxy.js is about as simple as it gets.  Our version live here at TES isn't much more complex than that!
I've been meaning to write an up to date blog post to describe how we use it fully here, with better production ready code examples - I'll use our next hack day here at Tes to do that.

+1
@cliftonc I'm waiting for your blog post to describe how we use it fully.
https://www.youtube.com/watch?v=l1GmfbblLcE great talk and awesome insight. Compoxure is very interesting and we hope it can help us to decompose our website and leverage our culture.

Thanks for the nudge, I'll see if I can carve out the time do pull this together.

I've created a simple project that mimics the service we have in production here at Tes:
https://github.com/tes/compoxure-example.

I've also now added a layout service, that demonstrates how we use a shared layout and slots to do an additional level of composition.


Make joystick visible by default in semi mode

I want to show joystick once plugin is initialized, not on click. I tried static mode but in that I want just the joystick to move and keep outer circle stationary as it is now. I'd like to have your recommendations. Thanks

I'm not sure I understand, this is what static does.
Have you tried the examples in static mode ? http://yoannmoinet.github.io/nipplejs/#demo

@yoannmoinet Yes, in other words static mode with a moving joystick.

So, I don't have much free time at the moment. So if you really need this, please feel free to take a shot at it and submit a PR, I'll be more than happy to review it.

Sorry for the confusion. It turns out I have missed position property when I tested static mode. This made the joystick not moveable. All good when I set 50%-50% for left and top.
Thanks for creating this awesome library.


Usage of pytest addopts with xdist

Hi guys,
first of all, I really love this plugin.
I recently added "--dist loadfile" to the addopts's of pytest (used by pytest-xdist). Since then, the plugin doesn't work anymore. Any clue?
Best regards,
Kai

Thanks for using the plugin and reporting the issue Kai!
After checking, it turns out to be this lazy hack where I invoke a pytest session to collect the names of fixtures: https://github.com/reverbc/pylint-pytest/blob/pylint-pytest-0.3.0/pylint_pytest/checkers/fixture.py#L74-L77
If a pytest.ini (or other equivalent configuration files) is present with pytest-xdist plugin + below config:
[pytest]
addopts = --dist loadfile

pytest will not be able to execute. We can view the stderr by invoking the command manually:
$ pytest --fixtures
================ test session starts ================
platform darwin -- Python 3.8.3, pytest-6.2.2, py-1.10.0, pluggy-0.13.1
rootdir: /Users/reverbc/Workspace/pylint-pytest/sandbox, configfile: pytest.ini
plugins: xdist-2.2.1, forked-1.3.0
ERROR: MISSING test execution (tx) nodes: please specify --tx

This can be fixed by appending --collect-only to that lazy hack pytest invocation so that pytest-xdist will basically ignore --dist loadfile since we're collecting only and not going to distribute them into workers.
PR will be out in a few seconds.


Update lstchain config and version to v0.9.7

Being discussed on slack now, https://github.com/cta-observatory/cta-lstchain/pull/1028 proposed a solution and we will release v0.9.7.post1 if there are no other problems or v0.9.8 if there are additional changes


Create Shift_FFT_data.py

For this assignment all pull requests going  forward should contain the following.
Title

This Pull request contain preparation.py file to shift the FFT data

Linting

Not done yet.

@ubsuny/cp1-24 Does anyone want to volunteer to review this?

ill volunteer for review

To do this you need to go back to your branch and open up the preparation.py in your codespace then copy past it in that already made file (called preparation.py) and only push that one, also if you do it soon you are not going to have to deal with merge conflicts (if you don't delete anything pre-existing in the file, meaning the defined dummy() function)

I am closing this pull request. I have created new one.


Pytest-mypy treats mypy annotation-unchecked warning as error

Since mypy 0.990, mypy emits a warning if a variable is annotated in a function without type annotation, see mypy 0.990 release notes.
Such a warning ends up being reported as a test failure in pytest-mypy, erroneously.

Thanks for the report :slightly_smiling_face: I am able to reproduce it.


Add label search to sign-invoice

Right now the sign-invoice command selects the first key it finds with the proper role. The command should be able to select using an exact label (--label) or a label match (--label-match).

@thomastaylor312 can you assign this to me !!

Done!


Header status is not changing.

I think the status is correct on the Security screen but not correct on the header. The question had expired and the status was showing red. While the header did not change the status.

Verified this issue on dev app v2.0.01(374)


Filter by Network Does Not Filter Past First Page

Introduced in #1192
See a video here on steps to reproduce:
https://www.loom.com/share/c3df2cd252474514b35e9772bcfb9f9f
I can take on creating a PR to address it

This PR fixes the issue - https://github.com/thirdweb-dev/dashboard/pull/1205

This PR fixes the issue - #1205

Sorry @MananTank just saw this - I also opened #1206 just now. Ill give your branch a quick test!

Heads up that I can get two Show More buttons - I'll see if I can whip up a fix for that

Let's go with https://github.com/thirdweb-dev/dashboard/pull/1206


add Statistics in the physical format

Is your feature request related to a problem or challenge?
Now when i get a physical plan like that:
❯ explain select test1.id,test2.int_col from test1 join test2 on test1.id = test2.bigint_col;
+---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+
| plan_type     | plan                                                                                |
+---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+
| logical_plan  | Projection: test1.id, test2.int_col                                                                                |
|               |   Inner Join: CAST(test1.id AS Int64) = test2.bigint_col                                                                                |
|               |     TableScan: test1 projection=[id]                                                                                |
|               |     TableScan: test2 projection=[int_col, bigint_col]                                                                                |
| physical_plan | ProjectionExec: expr=[id@0 as id, int_col@1 as int_col]                                                                                |
|               |   ProjectionExec: expr=[id@0 as id, int_col@2 as int_col, bigint_col@3 as bigint_col]                                                                           |
|               |     CoalesceBatchesExec: target_batch_size=8192                                                                                |
|               |       HashJoinExec: mode=CollectLeft, join_type=Inner, on=[(CAST(test1.id AS Int64)@1, bigint_col@1)]                                                           |
|               |         ProjectionExec: expr=[id@0 as id, CAST(id@0 AS Int64) as CAST(test1.id AS Int64)]                                                                       |
|               |           ParquetExec: file_groups={1 group: [[Users/kliu3/Documents/arrow-ballista/target/debug/alltypes_plain.parquet]]}, projection=[id]                |
|               |         ParquetExec: file_groups={1 group: [[Users/kliu3/Documents/arrow-ballista/target/debug/alltypes_plain.parquet]]}, projection=[int_col, bigint_col] |
|               |                                                                                |
+---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------+
2 rows in set. Query took 0.136 seconds.

But the physical plan missing the data of Statistics.
Can we add the Statistics in the physical plan format?
The struct of statistics is
pub struct Statistics {
    /// The number of table rows
    pub num_rows: Option<usize>,
    /// total bytes of the table rows
    pub total_byte_size: Option<usize>,
    /// Statistics on a column level
    pub column_statistics: Option<Vec<ColumnStatistics>>,
    /// If true, any field that is `Some(..)` is the actual value in the data provided by the operator (it is not
    /// an estimate). Any or all other fields might still be None, in which case no information is known.
    /// if false, any field that is `Some(..)` may contain an inexact estimate and may not be the actual value.
    pub is_exact: bool,
}

we can just log the num_rows, total_byte_size, is_exact and ignore the column_statistics
Describe the solution you'd like
append the Statistics in the DisplayAs trait
cc @alamb @jackwener
Describe alternatives you've considered
No response
Additional context
this will change many test cases for the plan

cc @mingmwang  @Ted-Jiang

we can just log the num_rows, total_byte_size, is_exact and ignore the column_statistics

I think showing the physical statistics to the explain output sounds like a good idea to me
Perhaps we could only show the statistics in EXPLAIN VERBOSE mode (so when DisplayFormatType::Verbose is passed to https://docs.rs/datafusion/latest/datafusion/physical_plan/display/trait.DisplayAs.html) ?


Prometheus and grafana datasource fixes

1)prometheus-grafana pipeline was not working because the prometheus-ingester container name was not available to scrape the metrics,fixed
2)grafana datasource addition was not working as the org_id, user_id, influx_token etc were not computed as influx and grafana containers were not up, added checks with sleep until containers are up
3)debug log for the setup script

This change with prometheus will fix the Issue #56


Faucet UI Improvements

Summary of changes

Improve the Faucet UI

Proposed area of change

[ ] apps/bridge-dapp
[ ] apps/hubble-stats
[ ] apps/stats-dapp
[ ] apps/webbsite
[x] apps/faucet
[ ] apps/tangle-website
[ ] libs/webb-ui-components

Reference issue to close (if applicable)

Closes https://github.com/webb-tools/webb-dapp/issues/1326
Closes https://github.com/webb-tools/webb-dapp/issues/1360

LGTM, let's merge it. 💪


publish the vsix file to github

fixed with https://github.com/camel-idea-plugin/camel-lsp-client-vscode/commit/0bc2d769ba0011b68dc802ce24c785ba98a8e865


faceapi is not defined

I'm encountering the "faceapi is not defined" error on an app that is only occurring on one of the sites we've got it installed on. The JavaScript file is loaded, but for some reason only on this one site, it can't seem to find the global faceapi object.
I am calling on faceapi from within another JavaScript file (and both files are dynamically added to the page via JavaScript), but that doesn't seem to be a problem on every site I've tried this on except this one. Any suggestions for what I might be able to try to track down the issue? It's like the global faceapi object doesn't exist.
EDIT: I've done some further testing and it appears nothing inside the face-api.js function is being called. If I add a console.log to the outside of it, I can confirm the file is loading. But if I place the same call just immediately inside the function, it never fires.

Further testing has allowed me to get it working, but I changed the face-api.js file as follows:
(function (global, factory) {   typeof exports === 'object' && typeof module !== 'undefined' ? factory(exports) :   typeof define === 'function' && define.amd ? define(['exports'], factory) :   (global = global || self, factory(global.faceapi = global.faceapi || {})); }(this, (function (exports) {'user strict';
Changed to:
(function (window) {     'use strict';     var exports = {};
And the very last line of face-api.js changed from this:
})));
to this:
window.faceapi = exports; }(window));
While it's working, I can't say I quite understand what I changed. What are the potential consequences of this change?


Apexcarts is not defined

Hello, I working local, without internet. U can add apexcarts js in packet, and add in config param local js or cdn js. Thanks

Please see my response here: https://github.com/akaunting/laravel-apexcharts/issues/5

Just fixed it in the new version.


Namespaced endpoints?

Can you have namespaced endpoints with wildcard?
For example:
endpoints.users.create = async function() {...}
endpoints.posts.create = async function() {...}

I know this is a bit semantics since you could have a createUser and createPost endpoints, but as the API surface grows being able to have namespaced routes becomes a valuable tool.

Closing this but if someone wants this let me know. I'm open to implement what Samuel said:

I imagine adding this type of functionality would not be too difficult if someone really wanted it since endpoints is just a proxy which could be modified to handle objects with function keys as well as simple functions.


Removed many small modules which were just making the current version…

… of phaseflow harder to read

Somehow these changes broke convection in the melting PCM test:

This was superseded by PR #144 .


[webapi] Sync MediaCapture upstream tests

Impacted TCs num(approved): New 0, Update 3, Delete 0
Unit test Platform: Crosswalk Project for Android 19.48.491.0
Unit test result summary: Pass 2, Fail 0, Blocke 1

Unit test result summary: Pass 2, Fail 0, Blocke 1

Which one is blocked?

mediastreamtrack-end-manual.html


Parsing error: Cannot find module 'babel-eslint'

issues: @vue/eslint-config-standard &<EMAIL_ADDRESS>Hi, I'm using @vue/eslint-config-standard  in my project. When install  eslint-plugin-vue: ^7.0.0, which is based on<EMAIL_ADDRESS>I find there're both babel-eslint (obsolete , lead to fail of installation) and @babel/eslint-parser in package.json. So i can't use the lastest version of @vue/eslint-config-standard.
Possible solutions:

Delete the babel-eslint in<EMAIL_ADDRESS>

vue-eslint-parser has no babel-eslint dependency. The same is true for v7.11.0.
https://github.com/vuejs/vue-eslint-parser/blob/v7.11.0/package.json#L12-L23

@ota-meshi well, it's in devDependencies at least.


BUG: fmin_powell return for size 1 array

Fixes #12298. However, I think the original behaviour was a bug. The original behaviour for fmin_powell was:
x0 = np.array([0.])
x0.shape = (1,)
x0.size = 1

# the result array is
res.x = np.array(0.)
res.x.shape = ()
res.x.size=1

This PR ensures back compatibility. However, I think the desired behaviour should be:
res.x = np.array([0.])
res.x.shape = (1,)
res.x.size = 1

If it's important to maintain this (buggy?) back compatibility then we should merge the PR and make sure it gets cherry picked into 1.5.0 (@tylerjereddy ).
@pv, @josef-pkt

I had read this wrong. I thought the problem was fopt and not xopt
I look into it more closely. I don't see a reason why xopt needs to be converted to a scalar/shape ( )

a previous issue #9715 for the inconsistent x shape in powell
In any case, statsmodels shouldn't bother about the shape of xopt and I will change that unit test.
In the original version, 7 years ago, the assert in the unit test was on a different value, and was changed 6 years ago to assert the shape of xopt.
In general, statsmodels would need xopt (our params) to be atleast 1d, but I don't think that we have many real unit tests with only a single parameter.

aside: statsmodels doesn't use powell much, not in defaults and not much in unit tests, because the performance of powell was worse than Nelder-Mead fmin when I looked at it many years ago.

In #9715 @rgommers mentions that back compat is retained for fmin_powell, even if it is inconsistent. Ralf, does that position still apply?

I verified, the current powell with shape ( ) breaks statsmodels fitting, it breaks the computation of the Hessian when there is only a single parameter.
So from the statsmodels perspective,  fmin_powell xopt shape ( ) is a bug.
my case for checking (as reminder here),
endog is just some count data that I had to look at a problem unrelated to scipy.
model_poi2 = sm.Poisson(endog=endog, exog=np.ones(len(endog))[:, None])
results_poi2 = model_poi2.fit(method='powell', maxiter=2000, disp=True, start_params=[1.], skip_hessian=True)
results_poi2.params.shape
()

In our usual case skip_hessian=False, I get a linalg error with wrong shape/dimension when computing the Hessian.
(So, the unit test in statsmodels check backwards compatibility for preserving the bug :)

@andyfaff @josef-pkt What's the status here as we approach within about 2 weeks of branching for 1.6.0?

I would prefer to close this PR, and for the original issue to be closed. AFAICT it came about because statsmodels was working around a bug/weird behaviour, and was checking that the scipy bug still existed.
@josef-pkt, would you concur, can we close this PR and original issue?

@josef-pkt after reading gh-12298 and seeing that statsmodels/statsmodels#6771 is closed, I think I'd agree with @andyfaff that this and gh-12298 can be closed. Do you agree?

@andyfaff Thanks for preparing this, but I agree with you that it's more appropriate to close gh-12298, so I'll go ahead and close this for you, too. (Maybe don't delete the branch unless @josef-pkt disagrees, though!)


pdfjs控件打印不清晰

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version:
Operating system and its version:
PDF.js version:
Is a browser extension:

Steps to reproduce the problem:
1.
2.
What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Please stop spamming this bug tracker with empty and/or non-English issues.


added display message and validation #962

What does this PR do?
Fixes #962 Add Form Validation and Success Message for Wildlife Conservation Form Submission

Adds form validation for the textarea input.
Displays a success message on valid submission.
Shows an error message if the textarea is left empty.

Please see the conflicts . Resolve the conflicts . Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


Not recieving notifications both android or ios

i just ifnished installed this plugin, was testing it and found i'm getting no notifications at all. they are neither shown nor catched by the events. the token is retrieved correctly and firebase reacts positively to sending him events.
my code:
`Firebase.getToken()
.then(token => console.log("The token is ${token}")) // save the token server-side and use it to push notifications to this device
.catch(error => console.error("Error getting token", error));
  Firebase.onTokenRefresh()
    .subscribe((token: string) => console.log("Got a new token ${token}"));

  Firebase.logEvent("HI",{}).then(token => console.log("event sent")) // save the token server-side and use it to push notifications to this device
    .catch(error => console.error("Error sending event", error));
  Firebase.onNotificationOpen().subscribe(data => {
    console.log("YAAY" + data);
  }, error => {
    console.log("NOOO" + error);
  });`

I'm using ionic v2 + angular 2

Just try this link it might help you, its use to send FCM notification,If u got any notification from this link,Your client side working and you need check your backed service
"http://pushtry.com/"

I'm not even using curl, i'm throwing them from the firebase console.

just try to use in your real device. Are you getting Token..?

yes, i'm only using real devices. no web/serve. both get token, both get a success on sending events, none gets notifications.

just save the token in DB,Copy that token and try it in above mention link!

"Firebase Push Notification successfully sent" ->  no notification on any device.

Check the that your app is foreground or background!

doesn't work, wathever the mode be. The notifications are not even showing in the notification tray. they're not being recieved by the devices.

uninstall the plugin and try it once!

Already tried, ended up testing cordova-plugin-fcm and it works, there must be some weird issue

You are not registering the callbacks in onNotificationOpen as per the docs:
window.FirebasePlugin.onNotificationOpen(function(notification) {
console.log(notification);
}, function(error) {
console.error(error);
});

I'm using ionicv2 with typescript, i can't use the callbacks as per the docs.
Firebase console is the main core of firebase, if it doesn't work there, how do i make sure notifications are working before making my own service?  http://pushtry.com/ didn't work either

For me, a mistake was an invalid android app package name in Firebase project settings. I found a solution here: http://stackoverflow.com/a/39262282/3877938
Pay attention to the statement:

Add your Package Name, which is the id of your app: you can see it in your config.xml (something like id="com.ionicframework.someTest123").

closing for now, reopen if still an issue with the latest version of the plugin


Migrate /fetchers/*.js files to TypeScript so we can share codes with the /lib/*.ts ones

Yes, I can't simply export lib/string-utils.ts because of the language difference.
Probably work if the configuration is updated or use additional library. But it'll take some time to explore and can affect the other part, so it'll be great if someone can help
Originally posted by @ekamuktia in https://github.com/kawalcovid19/wargabantuwarga.com/pull/136#discussion_r671910801
Tasks

[ ] Use ts-node instead of node to execute fetcher scripts.
[ ] Add JSDoc types to all helper functions in fetcher files.
[ ] Migrate all helper functions in fetcher files to /lib/*.ts.

Tasks list added.

Can I work on this?

Yes, of course.
According to our contributing guidelines, please create a draft pull request to signal the other contributors that you have started working on this issue, thanks, @Namchee!


[BUG] Windows Password never available on Jenkins after recent PRs

After #289 #291 #292 #293 #294 #295 #296, windows stuck on not able to boot and get password.
EC2 (Amazon_ec2_cloud) - jenkinsAgentNode-Jenkins-Agent-Windows2019-X64-C524xlarge-Single-Host
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.
Waiting for password to be available. Sleeping 10s.

Seems like able to connect here:
Connecting to (<IP_ADDRESS>) with WinRM as Administrator

Wonder why it is stucking right now.

Right after attempt to connect it failed:

Waiting for WinRM to come up. Sleeping 10s.

HTTP ERROR 404 Not Found

URI: | /manage/computer/EC2%20%28Amazon%5Fec2%5Fcloud%29%20%2D%20jenkinsAgentNode%2DJenkins%2DAgent%2DWindows2019%2DX64%2DC524xlarge%2DSingle%2DHost%20%28i%2D019b97c099c560adc%29/logText/progressiveHtml
-- | --
404
Not Found
Stapler

Manually remove queue:
[hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6315, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6330, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6331, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6332, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6333, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6334, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6335, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6337, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6373, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6374, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6397, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6402, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6403, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6404, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6415, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6419, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6430, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6431, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6436, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6441, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6442, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6443, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6446, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6447, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6448, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6449, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6450, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6451, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6452, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6453, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6454, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6455, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6456, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6461, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6475, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6493, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6495, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6499, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6503, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6533, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6534, hudson.model.Queue$BlockedItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@2ec5a7fc[gradle-check]:6535]

Switch all the agents on build.ci.opensearch.org for windows back to 2023/05/19 versions.

The above old ami confirms to connect with Jenkins

Waiting for password to be available. Sleeping 10s.
Connecting to (<IP_ADDRESS>) with WinRM as Administrator
Waiting for WinRM to come up. Sleeping 10s.
Waiting for WinRM to come up. Sleeping 10s.
Waiting for WinRM to come up. Sleeping 10s.
Connected with WinRM.
Creating tmp directory if it does not exist
Executing init script

C:\Users\Administrator>echo
ECHO is on.
init script ran successfully
remoting.jar sent remotely. Bootstrapping it
Launching via WinRM:java  -jar C:\Windows\Temp\remoting.jar -workDir C:/Users/Administrator/jenkins

Testing 2023/05/25 troubled AMI on personal account.

Test running normal windows without any issues on connection, very weird.

Possibly is the 300 seconds connection timeout is not enough on the new ami, will test next week on that.

Seems like the loading time of the new AMI is longer even when manually logging in.

Seems like stucking on this for a while:

Takes 3 times longer just to get into Windows desktop.

Seeing some errors:

ERROR: Timed out after 1007 seconds of waiting for winrm to be connected
com.amazonaws.AmazonClientException: Timed out after 1007 seconds of waiting for winrm to be connected
	at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:142)
	at hudson.plugins.ec2.win.EC2WindowsLauncher.launchScript(EC2WindowsLauncher.java:52)
	at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48)
	at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:298)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:80)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

After removing cypress the connection is ontime now.

Since cypress can be cached by npm install during ftrepo run, and does have windows native exe anyway, I will remove the cypress installation from the script for now.

The cypress is cached in %localappdata%\Cache (\AppData\Local\Cache) on windows by default which is different from ~/.cache in nix*.
Seems related:

https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/performance-issues-custom-default-user-profile

Still not fully fix the old one takes 6010seconds while the new one takes 9010seconds or so.
Even if it login it will still error out due to timeout.

Executing init script

C:\Users\Administrator>echo
ECHO is on.
init script ran successfully
remoting.jar sent remotely. Bootstrapping it
Launching via WinRM:java  -jar C:\Windows\Temp\remoting.jar -workDir C:/Users/Administrator/jenkins

<===[JENKINS REMOTING CAPACITY]===>Remoting version: 3107.v665000b_51092
Launcher: EC2WindowsLauncher

Communication Protocol: Standard in/out

This is a Windows agent

HTTP ERROR 404 Not Found

URI: | /manage/computer/EC2%20%28Amazon%5Fec2%5Fcloud%29%20%2D%20jenkinsAgentNode%2DJenkins%2DAgent%2DWindows2019%2DX64%2DC54xlarge%2DSingle%2DHost%20%28i%2D009b281124464ab3a%29/logText/progressiveHtml
-- | --
404
Not Found
Stapler

Seems like the delay is caused by adding scoop cache rm --all for some reason. Remove the line significantly boost the speed of startup.

I combined the above steps and increase timeouts of boot up on Windows Agent, eventually get both it connected on Windows after 16-20min each boot, slightly longer than previous boot time of less than 15min.
Next time we can invest into pure server core windows, or even nano to improve time, we are currently using base version.


Keep future release even with no new closed pull requests or issues

When using the --future-release  option  it would be good to get the release noted in the CHANGELOG.md file with link to full changelog even if no pull requests/issues are closed.
This is good to capture the cases where there are commits done that we're not linked to any pull request or issue (perhaps not a good strategy. But it happens...)
Right now it will be completely omitted which is kinda confusing.

Hi! It makes sense. Also as soon as #51 will be implemented - you can easily add essential commits to your change log also! :wink:

Great stuff :+1:
Thanks.


python3Packages.elementpath: 1.4.6 -> 2.0.0

Motivation for this change
noticed it was out of date
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

https://github.com/NixOS/nixpkgs/pull/95529
8 packages built:
python37Packages.elementpath python37Packages.fints python37Packages.sepaxml python37Packages.xmlschema python38Packages.elementpath python38Packages.fints python38Packages.sepaxml python38Packages.xmlschema

Result of nixpkgs-review pr 95529 1

8 packages built:
- python37Packages.elementpath
- python37Packages.fints
- python37Packages.sepaxml
- python37Packages.xmlschema
- python38Packages.elementpath
- python38Packages.fints
- python38Packages.sepaxml
- python38Packages.xmlschema


Authentication during file upload

Hi,
We have a requirement where we need to upload a Zip file to a URL location. The issue is that a username/password has to be provided.
Is there any way to add in authentication to the upload feature?
Thanks,
Minu

Yes, you can add a proxy in front of your tus server which inspects the Authorization header and validates that it has the proper rights to upload a ZIP file. To set the Authorization header you can use the headers option for tus-js-client's tus.Upload. What exact value the Authorization header should have depends on your application and authentication model but that's a rough sketch how you can make it work.

Closing this issue due to inactivity. Feel free to leave a comment if you want to continue the discussion :)


msg.value throws unnecessary in non payable functions.

    function playGame(uint id) isPlayer() isGameTime() {

        // We don't want any more ether
        if (msg.value>0)
            throw;

This check has been made obsolete by the absence of the payable modifier in the function definition.

Nice. I removed it.


Update how-to-authenticate-an-imap-pop-smtp-application-by-using-oaut…

…h.md
Configurations described in "Register your application" is not necessary. We cannot use permissions of Microsoft Graph for IMAP, POP and SMTP access. As described in "Get an access token" section, we need to acquire access tokens of Outlook, not Microsoft Graph. And we don't need to add permissions in advance, because we can acquire access tokens dynamically using MSAL or Microsoft Identity Platform v2 endpoint.
And, "Enabled for users to sign-in?" setting of "Office 365 Exchange Online" is "Yes" by default. If this setting is "No", no one can use Exchange Online.
I did a similar document update in the following commit last year.
https://github.com/MicrosoftDocs/office-developer-exchange-docs/commit/47fc6e17c778a3e809d7daedeb811b707c985eac
Though I couldn't find the exact commit which the unnecessary configurations were added, the following commit is suspicious.
https://github.com/MicrosoftDocs/office-developer-exchange-docs/commit/99aead68a911ed31f1b1856736892747bf0daed4

Docs Build status updates of commit 13ddbf2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Behavior change when call wt

Windows Terminal version (or Windows build number)
1.11.2421.0
Other Software
KeePass
SSH
Steps to reproduce
At URL Overrides of KeePass I use this command:
cmd://wt -w 0 nt ssh {USERNAME}@{URL:RMVSCM}
Expected Behavior
An wt PowerShell window or a new PowerShell table if a windows is already open executing the command ssh to defined host.
Actual Behavior
An wt SSH window or a new SSH table if a windows is already open executing the command ssh to defined host.

If you establish a SSH profile, it's expected to run ssh.exe directly and bypass w shell as it will open a shell in the remote environment (such as bash). You could create a powershell profile with the commandline option of ssh if you want but that's just unnecessary overhead. This behavior hasn't changed so likely something in your settings changed.

@WSLUser I believe the report is, "wt -w 0 no longer uses the existing window" :smile:

I saw SSH and see description regarding SSH and didn't realize it had nothing to do with SSH. A simpler repro would have been nice.

I dont have any SSH profile.
Befere, calling "wt -w 0 nt ssh" opens a PS windows e execute ssh in PS, now opens a ssh window...

I realize now a "Defaults" Profile, is this existing before? My command is now calling this profile instead of Windows Power Shell Profile.

OH. So it does open in a new tab in the same window.
In 1.11, we changed the behavior of "nt" so that it uses a base profile that doesn't have any special customizations -- this is because it was confusing for users. In 1.10, if you run "wt cmd" you get a Command Prompt window, but the title says PowerShell and the icon is PowerShell.

Got it. Tks.


Investigate what's needed to get reloading Web3torrent pages working

Problem description :confused:
Right now reloading web3torrent page, we lose the existing channels and budget.
Describe the solution you'd like :rocket:
Investigate what's needed to get the page keep those data.

Off the bat, web3torrent does initialize, and thus does not communicate with the wallet on load. So, to view budgets on reload, wallet initialization would need to happen on load.
This used to be the case, and was changed for a specific reason (that I am unaware of.)

Currently we only call enable() web3torrent client when user initiates an upload or download action. The enable() function then relies on payment channel client to communicate with the wallet. I think it doesn't happen on load because we want better UX (?). We could change the code to let the communication happen on page load though.
Ideally, we store some session data somewhere (firebase? cookies?), so that when users refresh the page, we can retrieve the budget and channel data. The next question is figure the storage.
One crucial piece of data is the signing address. We can use it as a key to retrieve data from storage.
It's not clear to me how wallet generates those signing addresses. It seems to be random. It needs to be deterministic so that when we refresh the page, we can still find out the same address.
@andrewgordstewart @geoknee What do you think? Do I miss anything?

It's not clear to me how wallet generates those signing addresses. It seems to be random. It needs to be deterministic so that when we refresh the page, we can still find out the same address.

I confirm that the address generation is deterministic. I saw the random behaviour probably because my local indexdb was corrupted. The issue went away after I cleared local indexdb.

Currently we only call enable() web3torrent client when user initiates an upload or download action. The enable() function then relies on payment channel client to communicate with the wallet. I think it doesn't happen on load because we want better UX (?).

If we call the enable() function on page load, it change the behaviour.
Before: Approve budget prompt on upload
After: Approve budget prompt right away on page load
So we need to change the integration tests as well.
Do you guys see an issue with this? @andrewgordstewart @geoknee

It's not clear to me how wallet generates those signing addresses. It seems to be random. It needs to be deterministic so that when we refresh the page, we can still find out the same address.

I confirm that the address generation is deterministic. I saw the random behaviour probably because my local indexdb was corrupted. The issue went away after I cleared local indexdb.

Just to confirm, the address generation is random, but it should only happen once. So, getAddress should return a random address when the store is initialized, but once it is initialized, it should return the same address each time.
If we call the enable() function on page load, it change the behaviour.
Before: Approve budget prompt on upload
After: Approve budget prompt right away on page load
So we need to change the integration tests as well.

I think enable() used to be called on page load, and this was changed for a specific UX reason. I think @spersico would know this?

Two quick notes.

Calling ethereum.enable(), triggering a MetaMask pop-up, is best done after some sort of user action. This is an opinion held my me and some others that is mostly about avoiding pop-ups on page load if we can help it and instead associating them with user-triggered actions.

It should be possible to approve a budget without requiring ethereum.enable(), but we can't do this right now because approveBudgetAndFund is a single API method as opposed to approveBudget and fund. Just FYI.

As a follow-up to #2 above, it shouldn't be an issue to call GetBudget from web3torrent to the xstate-wallet on page load. If there is no budget, the method should return null (or equivalent) and if it is present then it should return the budget. There is no need for ethereum.enable() to be called in this situation.

@snario Good notes.
Above we are mainly concerning the WebTorrentPaidStreamingClient.enable() which enables the payment channel client. Sounds like we need to decouple we the enable() calls so that the payment channel client gets enabled on page load, but delay ethereum.enable() until upload/download. I will look into that and see if it's possible.

Looks like this issue will be addressed in https://github.com/statechannels/monorepo/pull/1528