Version 3.0.2 of Hygieia fails to build.

@tabladrum @Sbrenthughes @nireeshT @satishc1
I was using Hygieia v3.0.1 and had issues trying to get the Bitbucket collector from pulling commit history from a private repository. I did follow all the documentation. My dashboard consisted of Monitor (green - which showed that it was able to connect to my Bitbucket instance) and repo which was failing to collect the commits. The Bitbucket log showed that the request was returning a 401. When I tried to curl the same API using my Personal Access Token, I successfully got back all the commits. This could only mean that something was fiddling with my Personal Access Token that led to me getting a 401. I then stumbled upon the issue https://github.com/Hygieia/Hygieia/pull/2919 which suggests that the Personal Access Token is getting decrypted which is wrong. I have now freshly cloned the latest Hygieia repository and when I tried to build it, it failed.
Note: I have not re-built hygieia-core as I had built it earlier before building Hygieia v3.0.1
Hygieia]$ pwd
/home/user1/hygieia/Hygieia
Hygieia]$ mvn clean install package
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.capitalone.dashboard:api:jar:3.0.2-SNAPSHOT
[WARNING] The expression ${version} is deprecated. Please use ${project.version} instead.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.capitalone.dashboard:api-audit:jar:3.0.2-SNAPSHOT
[WARNING] The expression ${version} is deprecated. Please use ${project.version} instead.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jenkins-ci.plugins:hygieia-publisher:hpi:2.2.0-SNAPSHOT
[WARNING] 'parent.relativePath' of POM org.jenkins-ci.plugins:hygieia-publisher:2.2.0-SNAPSHOT (/hygieia/Hygieia/hygieia-jenkins-plugin/pom.xml) points at com.capitalone.dashboard:Hygieia instead of org.jenkins-ci.plugins:plugin, please verify your project structure @ line 15, column 13
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
 SUCCESS [  0.730 s]
[INFO] com.capitalone.dashboard:api 3.0.2-SNAPSHOT ........ FAILURE [  0.280 s]
[INFO] com.capitalone.dashboard:api-audit 3.0.2-SNAPSHOT ..  SKIPPED
[INFO] com.capitalone.dashboard:UI 3.0.2-SNAPSHOT ......... SKIPPED
[INFO] com.capitalone.dashboard:ui-tests 3.0.2-SNAPSHOT ... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  3.198 s
[INFO] Finished at: 2019-05-22T11:30:43+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project api: Could not resolve dependencies for project com.capitalone.dashboard:api:jar:3.0.2-SNAPSHOT: Could not find artifact com.capitalone.dashboard:core:jar:3.1.1-SNAPSHOT -> [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/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :api
Can you please advise if I may have missed anything to build Hygieia? Also the fix that has been put for GitHub collector that stops decrypting the Personal Access token, can you please confirm it has been put for the Bitbucket collector?

I would suggest running mvn clean install on core and then trying again.

@Sbrenthughes , thanks for the above. I have now rebuild the latest hygieia-core and have been able to make progress with building Hygieia where it was last failing.
It is now failing to "gulp build".
[INFO] Message:
[INFO]     An error occured in task 'html'.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] com.capitalone.dashboard:Hygieia 3.0.2-SNAPSHOT .... SUCCESS [  0.715 s]
[INFO] com.capitalone.dashboard:api 3.0.2-SNAPSHOT ........ SUCCESS [ 27.585 s]
[INFO] com.capitalone.dashboard:api-audit 3.0.2-SNAPSHOT .. SUCCESS [  9.935 s]
[INFO] com.capitalone.dashboard:nfrr-audit-collector 3.0.2-SNAPSHOT SUCCESS [  8.150 s]
[INFO] com.capitalone.dashboard:rally-collector 3.0.2-SNAPSHOT SUCCESS [  3.283 s]
[INFO] com.capitalone.dashboard:artifactory-artifact-collector 3.0.2-SNAPSHOT SUCCESS [  3.355 s]
[INFO] com.capitalone.dashboard:bamboo-build-collector 3.0.2-SNAPSHOT SUCCESS [  3.020 s]
[INFO] com.capitalone.dashboard:jenkins-build-collector 3.0.2-SNAPSHOT SUCCESS [  3.420 s]
[INFO] com.capitalone.dashboard:jenkins-cucumber-test-collector 3.0.2-SNAPSHOT SUCCESS [  2.902 s]
[INFO] com.capitalone.dashboard:jenkins-codequality 3.0.2-SNAPSHOT SUCCESS [  4.616 s]
[INFO] com.capitalone.dashboard:sonar-codequality-collector 3.0.2-SNAPSHOT SUCCESS [  3.227 s]
[INFO] com.capitalone.dashboard:aws-cloud-collector 3.0.2-SNAPSHOT SUCCESS [  4.406 s]
[INFO] com.capitalone.dashboard:aws-cloudwatch-collector 3.0.2-SNAPSHOT SUCCESS [  1.867 s]
[INFO] com.capitalone.dashboard:udeploy-deployment-collector 3.0.2-SNAPSHOT SUCCESS [  2.758 s]
[INFO] com.capitalone.dashboard:xldeploy-deployment-collector 3.0.2-SNAPSHOT SUCCESS [  3.247 s]
[INFO] com.capitalone.dashboard:jira-feature-collector 3.0.2-SNAPSHOT SUCCESS [ 10.045 s]
[INFO] com.capitalone.dashboard:versionone-feature-collector 3.0.2-SNAPSHOT SUCCESS [  2.545 s]
[INFO] com.capitalone.dashboard:gitlab-feature-collector 3.0.2-SNAPSHOT SUCCESS [  3.646 s]
[INFO] com.capitalone.dashboard:chat-ops-collector 3.0.2-SNAPSHOT SUCCESS [  0.641 s]
[INFO] com.capitalone.dashboard:appdynamics-performance-collector 3.0.2-SNAPSHOT SUCCESS [  2.755 s]
[INFO] com.capitalone.dashboard:bitbucket-scm-collector 3.0.2-SNAPSHOT SUCCESS [  2.657 s]
[INFO] com.capitalone.dashboard:github-scm-collector 3.0.2-SNAPSHOT SUCCESS [  3.162 s]
[INFO] com.capitalone.dashboard:github-graphql-scm-collector 3.0.2-SNAPSHOT SUCCESS [  3.744 s]
[INFO] com.capitalone.dashboard:gitlab-scm-collector 3.0.2-SNAPSHOT SUCCESS [  2.847 s]
[INFO] com.capitalone.dashboard:hpsm-cmdb-collector 3.0.2-SNAPSHOT SUCCESS [  3.214 s]
[INFO] com.capitalone.dashboard:nexus-iq-collector 3.0.2-SNAPSHOT SUCCESS [  2.880 s]
[INFO] com.capitalone.dashboard:score-collector 3.0.2-SNAPSHOT SUCCESS [  4.873 s]
[INFO] com.capitalone.dashboard:jira-xray-testresult-collector 3.0.2-SNAPSHOT SUCCESS [ 29.032 s]
[INFO] Hygieia Publisher Plugin 2.2.0-SNAPSHOT ............ SUCCESS [ 45.746 s]
[INFO] com.capitalone.dashboard:UI 3.0.2-SNAPSHOT ......... FAILURE [ 54.567 s]
[INFO] com.capitalone.dashboard:ui-tests 3.0.2-SNAPSHOT ... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  04:17 min
[INFO] Finished at: 2019-05-22T17:36:57+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:gulp (gulp build) on project UI: Failed to run task: 'gulp build' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :UI
I tried running the command manually under UI folder as well. Following is what I got. Kindly advise.
[ Hygieia]$ cd UI
[ UI]$ gulp build
#[17:37:54] Using gulpfile /hygieia/Hygieia/UI/gulpfile.js
[17:37:54] Starting 'build'...
[17:37:54] Starting 'clean'...
[17:37:54] Finished 'clean' after 82 ms
[17:37:54] Starting 'assets'...
[17:37:54] Starting 'themes'...
[17:37:54] Starting 'fonts'...
[17:37:54] Starting 'js'...
[17:37:54] Starting 'views'...
[17:37:54] Starting 'test-data'...
[17:38:04] Finished 'themes' after 9.8 s
[17:38:04] Finished 'assets' after 9.85 s
[17:38:04] Finished 'views' after 9.97 s
[17:38:04] Finished 'js' after 10 s
[17:38:04] Finished 'test-data' after 10 s
[17:38:11] Finished 'fonts' after 17 s
[17:38:11] Starting 'html'...
[17:38:20] 'html' errored after 9.25 s
[17:38:20] RangeError: Maximum call stack size exceeded
at String.replace ()
at globUnescape (/hygieia/Hygieia/UI/node_modules/minimatch/minimatch.js:918:12)
at Minimatch.parse (/hygieia/Hygieia/UI/node_modules/minimatch/minimatch.js:617:12)
at Array.map ()
at Minimatch. (/hygieia/Hygieia/UI/node_modules/minimatch/minimatch.js:182:14)
at Array.map ()
at Minimatch.make (/hygieia/Hygieia/UI/node_modules/minimatch/minimatch.js:181:13)
at new Minimatch (/hygieia/Hygieia/UI/node_modules/minimatch/minimatch.js:136:8)
at setopts (/hygieia/Hygieia/UI/node_modules/npm-wiredep/node_modules/glob/common.js:118:20)
at new GlobSync (/hygieia/Hygieia/UI/node_modules/npm-wiredep/node_modules/glob/sync.js:40:3)
[17:38:20] 'build' errored after 27 s
[17:38:20] Error in plugin 'run-sequence'
Message:
An error occured in task 'html'.
[UI]$

Can you cd directly to the UI folder and run npm install

@Sbrenthughes , I ran npm install under the UI folder.
UI]$ npm install
up to date in 8.636s
I then re-ran
Hygieia]$ mvn clean install package -rf :UI
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.capitalone.dashboard:api:jar:3.0.2-SNAPSHOT
[WARNING] The expression ${version} is deprecated. Please use ${project.version} instead.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.capitalone.dashboard:api-audit:jar:3.0.2-SNAPSHOT
[WARNING] The expression ${version} is deprecated. Please use ${project.version} instead.
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jenkins-ci.plugins:hygieia-publisher:hpi:2.2.0-SNAPSHOT
[WARNING] 'parent.relativePath' of POM org.jenkins-ci.plugins:hygieia-publisher:2.2.0-SNAPSHOT (/hygieia/Hygieia/hygieia-jenkins-plugin/pom.xml) points at com.capitalone.dashboard:Hygieia instead of org.jenkins-ci.plugins:plugin, please verify your project structure @ line 15, column 13
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] com.capitalone.dashboard:UI                                        [pom]
[INFO] com.capitalone.dashboard:ui-tests                                  [jar]
[INFO]
[INFO] --------------------< com.capitalone.dashboard:UI >---------------------
[INFO] Building com.capitalone.dashboard:UI 3.0.2-SNAPSHOT                [1/2]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ UI ---
[INFO]
[INFO] >>> maven-pmd-plugin:3.6:check (default) > :pmd @ UI >>>
[INFO]
[INFO] --- maven-pmd-plugin:3.6:pmd (pmd) @ UI ---
[INFO]
[INFO] <<< maven-pmd-plugin:3.6:check (default) < :pmd @ UI <<<
[INFO]
[INFO]
[INFO] --- maven-pmd-plugin:3.6:check (default) @ UI ---
[INFO]
[INFO] --- jacoco-maven-plugin:<IP_ADDRESS>602180812:prepare-agent (default) @ UI ---
[INFO] argLine set to -javaagent:/home/user1/.m2/repository/org/jacoco/org.jacoco.agent/<IP_ADDRESS>602180812/org.jacoco.agent-<IP_ADDRESS>602180812-runtime.jar=destfile=/hygieia/Hygieia/UI/target/jacoco.exec
[INFO]
[INFO] --- frontend-maven-plugin:1.6:install-node-and-npm (install node and npm) @ UI ---
[INFO] Found proxies: [optional{protocol='http', host='my-company-proxy', port=9595, with username/passport authentication}]
[INFO] Node v6.9.1 is already installed.
[INFO] NPM 5.0.1 is already installed.
[INFO]
[INFO] --- frontend-maven-plugin:1.6:npm (npm install) @ UI ---
[INFO] Found proxies: [optional{protocol='http', host='my-company-proxy', port=9595, with username/passport authentication}]
[INFO] Running 'npm install --ignore-scripts --https-proxy=http://EID:***@my-company-proxy:9595 --proxy=http://EID:***@my-company-proxy:9595' in /hygieia/Hygieia/UI
[INFO] up to date in 6.843s
[INFO]
[INFO] --- frontend-maven-plugin:1.6:gulp (gulp build) @ UI ---
[INFO] Running 'gulp build' in /hygieia/Hygieia/UI
[INFO] [10:11:23] Using gulpfile /hygieia/Hygieia/UI/gulpfile.js
[INFO] [10:11:23] Starting 'build'...
[INFO] [10:11:23] Starting 'clean'...
[INFO] [10:11:23] Finished 'clean' after 57 ms
[INFO] [10:11:23] Starting 'assets'...
[INFO] [10:11:23] Starting 'themes'...
[INFO] [10:11:23] Starting 'fonts'...
[INFO] [10:11:23] Starting 'js'...
[INFO] [10:11:23] Starting 'views'...
[INFO] [10:11:23] Starting 'test-data'...
[INFO] [10:11:35] Finished 'themes' after 12 s
[INFO] [10:11:35] Finished 'assets' after 12 s
[INFO] [10:11:35] Finished 'test-data' after 12 s
[INFO] [10:11:36] Finished 'views' after 13 s
[INFO] [10:11:36] Finished 'js' after 13 s
[INFO] [10:11:48] Finished 'fonts' after 25 s
[INFO] [10:11:48] Starting 'html'...
[INFO] [10:11:56] 'html' errored after 7.94 s
[INFO] [10:11:56] RangeError: Maximum call stack size exceeded
[INFO]     at /hygieia/Hygieia/UI/node_modules/npm-wiredep/lib/detect-dependencies.js:149:29
[INFO]     at /hygieia/Hygieia/UI/node_modules/lodash/lodash.js:4911:15
[INFO]     at baseForOwn (/hygieia/Hygieia/UI/node_modules/lodash/lodash.js:2996:24)
[INFO]     at /hygieia/Hygieia/UI/node_modules/lodash/lodash.js:4880:18
[INFO]     at Function.forEach (/hygieia/Hygieia/UI/node_modules/lodash/lodash.js:9344:14)
[INFO]     at /hygieia/Hygieia/UI/node_modules/npm-wiredep/lib/detect-dependencies.js:183:11
[INFO]     at /hygieia/Hygieia/UI/node_modules/lodash/lodash.js:4911:15
[INFO]     at baseForOwn (/hygieia/Hygieia/UI/node_modules/lodash/lodash.js:2996:24)
[INFO]     at /hygieia/Hygieia/UI/node_modules/lodash/lodash.js:4880:18
[INFO]     at Function.forEach (/hygieia/Hygieia/UI/node_modules/lodash/lodash.js:9344:14)
[INFO]     at /hygieia/Hygieia/UI/node_modules/npm-wiredep/lib/detect-dependencies.js:183:11
[INFO] [10:11:56] 'build' errored after 33 s
[INFO] [10:11:56] Error in plugin 'run-sequence'
[INFO] Message:
[INFO]     An error occured in task 'html'.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for com.capitalone.dashboard:UI 3.0.2-SNAPSHOT:
[INFO]
[INFO] com.capitalone.dashboard:UI ........................ FAILURE [ 42.855 s]
[INFO] com.capitalone.dashboard:ui-tests .................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  45.312 s
[INFO] Finished at: 2019-05-23T10:11:56+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:gulp (gulp build) on project UI: Failed to run task: 'gulp build' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] `http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException```

I get the same error. Kindly advise.

What version of maven are you using

~]$ mvn -v Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T19:41:47+01:00) Maven home: /home/user1/apache-maven-3.6.0 Java version: 1.8.0_191, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>.b12-1.el7_6.x86_64/jre Default locale: en_GB, platform encoding: UTF-8 OS name: "linux", version: "3.10.0-514.16.1.el7.x86_64", arch: "amd64", family: "unix"

@Sbrenthughes , have you been able to replicate this issue?

@ParashmaniD We will be performing a Maven Release this week and will update you once its done.

@rvema any updates please?

@ParashmaniD Still working on it, Meanwhile can you try checkout of source code from master branch and build using mvn clean install?

Hi,
I am having this issue as well when trying to build the latest hygieia from the latest master branch.
Below the error after executing gulp build
RangeError: Maximum call stack size exceeded
    at String.replace (<anonymous>)
    at globUnescape (C:\github\Hygieia\UI\node_modules\npm-wiredep\node_modules\minimatch\minimatch.js:918:12)
    at Minimatch.parse (C:\github\Hygieia\UI\node_modules\npm-wiredep\node_modules\minimatch\minimatch.js:617:12)
    at Array.map (<anonymous>)
    at Minimatch.<anonymous> (C:\github\Hygieia\UI\node_modules\npm-wiredep\node_modules\minimatch\minimatch.js:182:14)
    at Array.map (<anonymous>)
    at Minimatch.make (C:\github\Hygieia\UI\node_modules\npm-wiredep\node_modules\minimatch\minimatch.js:181:13)
    at new Minimatch (C:\github\Hygieia\UI\node_modules\npm-wiredep\node_modules\minimatch\minimatch.js:136:8)
    at setopts (C:\github\Hygieia\UI\node_modules\npm-wiredep\node_modules\glob\common.js:118:20)
    at new GlobSync (C:\github\Hygieia\UI\node_modules\npm-wiredep\node_modules\glob\sync.js:40:3)

@rvema , thanks for your response. I have followed your instructions.
I have checked out the latest version of hygieia-core. The latest commit on my local master is 05c927137251a7f576d46b335e463e624bd97419
I have then build the project successfully.
I have checked out the latest version of Hygieia. The latest commit on my local master is 0c5c0f3a45ae44246150d159636d0f3961e31342
I have tried to rebuild the project and it fails exactly in the same place.
[INFO] --- frontend-maven-plugin:1.6:gulp (gulp build) @ UI ---
[INFO] Running 'gulp build' in /hygieia/Hygieia/UI
[INFO] [13:55:43] Using gulpfile /hygieia/Hygieia/UI/gulpfile.js
[INFO] [13:55:43] Starting 'build'...
[INFO] [13:55:43] Starting 'clean'...
[INFO] [13:55:43] Finished 'clean' after 69 ms
[INFO] [13:55:43] Starting 'assets'...
[INFO] [13:55:43] Starting 'themes'...
[INFO] [13:55:43] Starting 'fonts'...
[INFO] [13:55:43] Starting 'js'...
[INFO] [13:55:43] Starting 'views'...
[INFO] [13:55:43] Starting 'test-data'...
[INFO] [13:55:55] Finished 'themes' after 12 s
[INFO] [13:55:55] Finished 'assets' after 12 s
[INFO] [13:55:55] Finished 'test-data' after 12 s
[INFO] [13:55:55] Finished 'views' after 12 s
[INFO] [13:55:55] Finished 'js' after 12 s
[INFO] [13:56:19] Finished 'fonts' after 36 s
[INFO] [13:56:19] Starting 'html'...
[INFO] [13:56:27] 'html' errored after 7.55 s
[INFO] [13:56:27] RangeError: Maximum call stack size exceeded
[INFO]     at /hygieia/Hygieia/UI/node_modules/npm-wiredep/lib/detect-dependencies.js:149:29
[INFO]     at /hygieia/Hygieia/UI/node_modules/lodash/lodash.js:4911:15
[INFO]     at baseForOwn (/hygieia/Hygieia/UI/node_modules/lodash/lodash.js:2996:24)
[INFO]     at /hygieia/Hygieia/UI/node_modules/lodash/lodash.js:4880:18
[INFO]     at Function.forEach (/hygieia/Hygieia/UI/node_modules/lodash/lodash.js:9344:14)
[INFO]     at /hygieia/Hygieia/UI/node_modules/npm-wiredep/lib/detect-dependencies.js:183:11
[INFO]     at /hygieia/Hygieia/UI/node_modules/lodash/lodash.js:4911:15
[INFO]     at baseForOwn (/hygieia/Hygieia/UI/node_modules/lodash/lodash.js:2996:24)
[INFO]     at /hygieia/Hygieia/UI/node_modules/lodash/lodash.js:4880:18
[INFO]     at Function.forEach (/hygieia/Hygieia/UI/node_modules/lodash/lodash.js:9344:14)
[INFO]     at /hygieia/Hygieia/UI/node_modules/npm-wiredep/lib/detect-dependencies.js:183:11
[INFO] [13:56:27] 'build' errored after 44 s
[INFO] [13:56:27] Error in plugin 'run-sequence'
[INFO] Message:
[INFO]     An error occured in task 'html'.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] com.capitalone.dashboard:Hygieia 3.0.2-SNAPSHOT .... SUCCESS [  0.848 s]
[INFO] com.capitalone.dashboard:api 3.0.2-SNAPSHOT ........ SUCCESS [ 27.838 s]
[INFO] com.capitalone.dashboard:api-audit 3.0.2-SNAPSHOT .. SUCCESS [ 10.184 s]
[INFO] com.capitalone.dashboard:nfrr-audit-collector 3.0.2-SNAPSHOT SUCCESS [  8.466 s]
[INFO] com.capitalone.dashboard:rally-collector 3.0.2-SNAPSHOT SUCCESS [  3.615 s]
[INFO] com.capitalone.dashboard:artifactory-artifact-collector 3.0.2-SNAPSHOT SUCCESS [  3.247 s]
[INFO] com.capitalone.dashboard:bamboo-build-collector 3.0.2-SNAPSHOT SUCCESS [  3.212 s]
[INFO] com.capitalone.dashboard:jenkins-build-collector 3.0.2-SNAPSHOT SUCCESS [  3.612 s]
[INFO] com.capitalone.dashboard:jenkins-cucumber-test-collector 3.0.2-SNAPSHOT SUCCESS [  2.700 s]
[INFO] com.capitalone.dashboard:jenkins-codequality 3.0.2-SNAPSHOT SUCCESS [  4.245 s]
[INFO] com.capitalone.dashboard:sonar-codequality-collector 3.0.2-SNAPSHOT SUCCESS [  6.502 s]
[INFO] com.capitalone.dashboard:aws-cloud-collector 3.0.2-SNAPSHOT SUCCESS [  4.373 s]
[INFO] com.capitalone.dashboard:aws-cloudwatch-collector 3.0.2-SNAPSHOT SUCCESS [  1.905 s]
[INFO] com.capitalone.dashboard:udeploy-deployment-collector 3.0.2-SNAPSHOT SUCCESS [  2.691 s]
[INFO] com.capitalone.dashboard:xldeploy-deployment-collector 3.0.2-SNAPSHOT SUCCESS [  2.796 s]
[INFO] com.capitalone.dashboard:jira-feature-collector 3.0.2-SNAPSHOT SUCCESS [ 10.256 s]
[INFO] com.capitalone.dashboard:versionone-feature-collector 3.0.2-SNAPSHOT SUCCESS [  2.606 s]
[INFO] com.capitalone.dashboard:gitlab-feature-collector 3.0.2-SNAPSHOT SUCCESS [  3.493 s]
[INFO] com.capitalone.dashboard:chat-ops-collector 3.0.2-SNAPSHOT SUCCESS [  0.705 s]
[INFO] com.capitalone.dashboard:appdynamics-performance-collector 3.0.2-SNAPSHOT SUCCESS [  2.858 s]
[INFO] com.capitalone.dashboard:bitbucket-scm-collector 3.0.2-SNAPSHOT SUCCESS [  2.822 s]
[INFO] com.capitalone.dashboard:github-scm-collector 3.0.2-SNAPSHOT SUCCESS [  3.051 s]
[INFO] com.capitalone.dashboard:github-graphql-scm-collector 3.0.2-SNAPSHOT SUCCESS [  4.009 s]
[INFO] com.capitalone.dashboard:gitlab-scm-collector 3.0.2-SNAPSHOT SUCCESS [  3.157 s]
[INFO] com.capitalone.dashboard:hpsm-cmdb-collector 3.0.2-SNAPSHOT SUCCESS [  3.254 s]
[INFO] com.capitalone.dashboard:nexus-iq-collector 3.0.2-SNAPSHOT SUCCESS [  2.730 s]
[INFO] com.capitalone.dashboard:score-collector 3.0.2-SNAPSHOT SUCCESS [  4.845 s]
[INFO] com.capitalone.dashboard:jira-xray-testresult-collector 3.0.2-SNAPSHOT SUCCESS [ 21.488 s]
[INFO] Hygieia Publisher Plugin 2.2.0-SNAPSHOT ............ SUCCESS [01:07 min]
[INFO] com.capitalone.dashboard:UI 3.0.2-SNAPSHOT ......... FAILURE [ 54.437 s]
[INFO] com.capitalone.dashboard:ui-tests 3.0.2-SNAPSHOT ... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  04:36 min
[INFO] Finished at: 2019-06-04T13:56:27+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:gulp (gulp build) on project UI: Failed to run task: 'gulp build' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :UI
[user1@UKC9CS0000097 Hygieia]$

Kindly advise.

What is your node and npm versions?

[Hygieia]# npm -v
6.4.1
[Hygieia]# node -v
v6.14.0

@Sbrenthughes @rvema , have you been able to replicate this issue?

@ParashmaniD sorry for the delay, The release will happen this weekend. Please hang on

This error is still occurring with the latest master.
commit ffc845e421c7a8591a97a76b078ba7c52e8e947d (HEAD -> master, origin/master, origin/HEAD)
Author: chen<EMAIL_ADDRESS>Date:   Wed Jul 3 10:09:48 2019 +0800

gulp serve
[11:31:47] Using gulpfile ~/workspaces/Hygieia/Hygieia/UI/gulpfile.js
[11:31:47] Starting 'build'...
[11:31:47] Starting 'clean'...
[11:31:47] Finished 'clean' after 51 ms
[11:31:47] Starting 'assets'...
[11:31:47] Starting 'themes'...
[11:31:47] Starting 'fonts'...
[11:31:47] Starting 'js'...
[11:31:47] Starting 'views'...
[11:31:47] Starting 'test-data'...
[11:31:53] Finished 'themes' after 5.76 s
[11:31:53] Finished 'assets' after 5.79 s
[11:31:53] Finished 'views' after 5.87 s
[11:31:53] Finished 'test-data' after 5.94 s
[11:31:53] Finished 'js' after 5.96 s
[11:32:03] Finished 'fonts' after 16 s
[11:32:03] Starting 'html'...
[11:32:04] 'html' errored after 1.58 s
[11:32:04] RangeError: Maximum call stack size exceeded
at String.replace ()
at globUnescape (/Users/jim.haungs/workspaces/Hygieia/Hygieia/UI/node_modules/npm-wiredep/node_modules/minimatch/minimatch.js:918:12)
at Minimatch.parse (/Users/jim.haungs/workspaces/Hygieia/Hygieia/UI/node_modules/npm-wiredep/node_modules/minimatch/minimatch.js:617:12)
at Array.map ()
at Minimatch. (/Users/jim.haungs/workspaces/Hygieia/Hygieia/UI/node_modules/npm-wiredep/node_modules/minimatch/minimatch.js:182:14)
at Array.map ()
at Minimatch.make (/Users/jim.haungs/workspaces/Hygieia/Hygieia/UI/node_modules/npm-wiredep/node_modules/minimatch/minimatch.js:181:13)
at new Minimatch (/Users/jim.haungs/workspaces/Hygieia/Hygieia/UI/node_modules/npm-wiredep/node_modules/minimatch/minimatch.js:136:8)
at setopts (/Users/jim.haungs/workspaces/Hygieia/Hygieia/UI/node_modules/npm-wiredep/node_modules/glob/common.js:118:20)
at new GlobSync (/Users/jim.haungs/workspaces/Hygieia/Hygieia/UI/node_modules/npm-wiredep/node_modules/glob/sync.js:40:3)
[11:32:04] 'build' errored after 17 s
[11:32:04] Error in plugin 'run-sequence'
Message:
An error occured in task 'html'.

Getting similar : error on mvn clean install package
Reactor Summary: [INFO]  [INFO] com.capitalone.dashboard:Hygieia 3.0.2-SNAPSHOT .... SUCCESS [  0.606 s] [INFO] com.capitalone.dashboard:api 3.0.2-SNAPSHOT ........ SUCCESS [ 26.259 s] [INFO] com.capitalone.dashboard:api-audit 3.0.2-SNAPSHOT .. SUCCESS [  9.832 s] [INFO] com.capitalone.dashboard:nfrr-audit-collector 3.0.2-SNAPSHOT SUCCESS [  8.087 s] [INFO] com.capitalone.dashboard:rally-collector 3.0.2-SNAPSHOT SUCCESS [  3.439 s] [INFO] com.capitalone.dashboard:artifactory-artifact-collector 3.0.2-SNAPSHOT SUCCESS [  3.328 s] [INFO] com.capitalone.dashboard:bamboo-build-collector 3.0.2-SNAPSHOT SUCCESS [  3.092 s] [INFO] com.capitalone.dashboard:jenkins-build-collector 3.0.2-SNAPSHOT SUCCESS [  3.412 s] [INFO] com.capitalone.dashboard:jenkins-cucumber-test-collector 3.0.2-SNAPSHOT SUCCESS [  2.998 s] [INFO] com.capitalone.dashboard:jenkins-codequality 3.0.2-SNAPSHOT SUCCESS [  4.472 s] [INFO] com.capitalone.dashboard:sonar-codequality-collector 3.0.2-SNAPSHOT SUCCESS [  3.794 s] [INFO] com.capitalone.dashboard:aws-cloud-collector 3.0.2-SNAPSHOT SUCCESS [  6.047 s] [INFO] com.capitalone.dashboard:aws-cloudwatch-collector 3.0.2-SNAPSHOT SUCCESS [  3.532 s] [INFO] com.capitalone.dashboard:udeploy-deployment-collector 3.0.2-SNAPSHOT SUCCESS [  5.254 s] [INFO] com.capitalone.dashboard:xldeploy-deployment-collector 3.0.2-SNAPSHOT SUCCESS [  4.969 s] [INFO] com.capitalone.dashboard:jira-feature-collector 3.0.2-SNAPSHOT SUCCESS [ 18.216 s] [INFO] com.capitalone.dashboard:versionone-feature-collector 3.0.2-SNAPSHOT SUCCESS [  4.382 s] [INFO] com.capitalone.dashboard:gitlab-feature-collector 3.0.2-SNAPSHOT SUCCESS [  5.066 s] [INFO] com.capitalone.dashboard:chat-ops-collector 3.0.2-SNAPSHOT SUCCESS [  1.089 s] [INFO] com.capitalone.dashboard:appdynamics-performance-collector 3.0.2-SNAPSHOT SUCCESS [  3.101 s] [INFO] com.capitalone.dashboard:bitbucket-scm-collector 3.0.2-SNAPSHOT SUCCESS [  4.542 s] [INFO] com.capitalone.dashboard:github-scm-collector 3.0.2-SNAPSHOT SUCCESS [  3.205 s] [INFO] com.capitalone.dashboard:github-graphql-scm-collector 3.0.2-SNAPSHOT SUCCESS [  4.594 s] [INFO] com.capitalone.dashboard:gitlab-scm-collector 3.0.2-SNAPSHOT SUCCESS [  4.480 s] [INFO] com.capitalone.dashboard:hpsm-cmdb-collector 3.0.2-SNAPSHOT SUCCESS [  4.361 s] [INFO] com.capitalone.dashboard:nexus-iq-collector 3.0.2-SNAPSHOT SUCCESS [  3.696 s] [INFO] com.capitalone.dashboard:score-collector 3.0.2-SNAPSHOT SUCCESS [  5.431 s] [INFO] com.capitalone.dashboard:jira-xray-testresult-collector 3.0.2-SNAPSHOT SUCCESS [ 12.892 s] [INFO] Hygieia Publisher Plugin 2.2.2-SNAPSHOT ............ SUCCESS [ 40.053 s] [INFO] com.capitalone.dashboard:UI 3.0.2-SNAPSHOT ......... FAILURE [  1.276 s] [INFO] com.capitalone.dashboard:ui-tests 3.0.2-SNAPSHOT ... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time:  03:27 min [INFO] Finished at: 2019-07-17T12:35:09-05:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:install-node-and-npm (install node and npm) on project UI: Could not extract the Node archive: Could not extract archive: '/Users/z0029gt/.m2/repository/com/github/eirslett/node/6.9.1/node-6.9.1-darwin-x64.tar.gz': EOFException -> [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 <goals> -rf :UI
Let me know if I am missing something.
Cloned from the master: both hygieia-core repo and Hygieia repo

@rvema @Sbrenthughes  Do you have any updates please?

@ParashmaniD Can you check the v3.0.3 release? Also the master branch is pretty stable and we dont see any build issues with the same. Please confirm the same.

@ParashmaniD Did you get a chance to look into the above comments?

@rvema I have not had a chance. I will keep you posted when I try this in the next few days.

@ParashmaniD Let us know if you run into issues. Also we are in the process of splitting the components of Hygieia into their own repos under the Hygieia Org.

@rvema , apologies I have not been able to get back any sooner. We had to park the Hygieia story due to the issues we are having.
I have build hygieia-core fine . The Step 1 in initial set-up document http://hygieia.github.io/Hygieia/setup.html#build-hygieia suggests that
First you must build the Hygieia core. In the command line/terminal, run the following command from the \hygieia-core directory:

mvn clean install package
Next you must build the api. In the command line/terminal, run the following command from the \api directory:

mvn clean install package

I am guessing it means build Hygieia core first followed by running "mvn clean install package" inside the "api-audit" directory as there is no "api" directory.
I have done that and then ran "mvn clean install package" on the top level (outside api-audit) Hygieia directory. It did build fine.
[INFO] Reactor Summary:
[INFO]
[INFO] com.capitalone.dashboard:Hygieia 3.0.2-SNAPSHOT .... SUCCESS [  1.250 s]
[INFO] com.capitalone.dashboard:api-audit 3.0.2-SNAPSHOT .. SUCCESS [ 15.294 s]
[INFO] com.capitalone.dashboard:artifactory-artifact-collector 3.0.2-SNAPSHOT SUCCESS [  4.739 s]
[INFO] com.capitalone.dashboard:UI 3.0.3-SNAPSHOT ......... SUCCESS [01:03 min]
[INFO] com.capitalone.dashboard:ui-tests 3.0.2-SNAPSHOT ... SUCCESS [  0.614 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:25 min
[INFO] Finished at: 2019-08-27T16:59:54+01:00
[INFO] ------------------------------------------------------------------------

However I do need some clarification. I was expecting to see more collectors and not just artifactory. Is there a reason why other collectors aren't there?
Hygieia]# ll collectors/
total 8
drwxr-xr-x. 3 root root 4096 Aug 20 16:26 artifact
-rw-r--r--. 1 root root  156 Aug 20 16:26 README.md

Hygieia]# ll collectors/artifact/
total 4
drwxr-xr-x. 6 root root 4096 Aug 27 16:58 artifactory

Hygieia]# ll collectors/artifact/artifactory/
total 28
drwxr-xr-x.  2 root root 4096 Aug 20 16:26 docker
-rw-r--r--.  1 root root  355 Aug 20 16:26 Dockerfile
drwxr-xr-x.  2 root root 4096 Aug 27 16:34 logs
-rw-r--r--.  1 root root 3942 Aug 20 16:26 pom.xml
-rw-r--r--.  1 root root  166 Aug 20 16:26 README.md
drwxr-xr-x.  4 root root 4096 Aug 20 16:26 src
drwxr-xr-x. 10 root root 4096 Aug 27 16:58 target

Am I missing something here?
The commit from which I am building Hygieia is
commit b9d84c2a30d3f8b95a4d0590a103dca0a05c089b
Author: nireeshT<EMAIL_ADDRESS>Date:   Mon Aug 19 22:05:47 2019 -0400

    Audit binary artifacts (#3116)

    * Override artifactory collector - repo based - consolidate aritfacts with name and version with latest information

    * Artifact evaluator - audit binary artifacts with in time range

Additional information.
Hygieia]# mvn -v
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T19:41:47+01:00)
Maven home: /opt/maven
Java version: 1.8.0_212, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>.b04-0.el7_6.x86_64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-957.10.1.el7.x86_64", arch: "amd64", family: "unix"

@rvema I am trying to build the UI project and ending up with npm issues.
I have installed gulp successfully.
[root@servername UI]# npm install -g gulp
/usr/bin/gulp -> /usr/lib/node_modules/gulp/bin/gulp.js
/usr/lib
└─┬<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ └─┬<EMAIL_ADDRESS>  │   └──<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └──<EMAIL_ADDRESS>
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/gulp/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
[root@servername UI]#

But when I try to install the dependencies from the package.json, it fails.
[root@servername UI]# npm install

><EMAIL_ADDRESS>postinstall /root/hygieia/UI/node_modules/@angular/cli
> node ./bin/postinstall/script.js

module.js:478
    throw err;
    ^

Error: Cannot find module<EMAIL_ADDRESS>    at Function.Module._resolveFilename (module.js:476:15)
    at Function.Module._load (module.js:424:25)
    at Module.runMain (module.js:611:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:160:9)
    at bootstrap_node.js:507:3
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>- 3 but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm ERR! Linux 3.10.0-957.10.1.el7.x86_64
npm ERR! argv "/usr/bin/node" "/bin/npm" "install"
npm ERR! node v6.17.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>postinstall: `node ./bin/postinstall/script.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'node ./bin/postinstall/script.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @angular/cli package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./bin/postinstall/script.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @angular/cli
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @angular/cli
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /root/hygieia/UI/npm-debug.log
[root@servername UI]#

It is unable to find the cli.
[root@servernameUI]# ll node_modules/@angular/
animations/               compiler/                 flex-layout/              platform-browser/
cdk/                      compiler-cli/             forms/                    platform-browser-dynamic/
common/                   core/                     language-service/         router/
[root@UKC9DA0000248 UI]# ll node_modules/@angular/cli
ls: cannot access node_modules/@angular/cli: No such file or directory
[root@servrname UI]#

I am pointing to the latest on master.
[root@servername UI]# git log
commit d2e63ecb68aa193d355d3cfca196c05d934862f9
Merge: 208949b 9fab5eb
Author: jhoelscher7<EMAIL_ADDRESS>Date:   Thu Jul 25 16:40:38 2019 -0400

    Merge pull request #29 from jhoelscher7/gauge-chart

    Shared Gauge chart

commit 9fab5ebb9d42b245740f5615ac71379a4eb27f93
Merge: 67adc63 208949b

The NPM version installed is : 3.10.10
The node version installed is : v6.17.1
Kindly advise.

@rvema @Sbrenthughes : Could you please advise how to get past this issue?

the npm version looks little dated, we currently tested this v5.x

mvn clean install should install dependencies that are missing.

@rvema I followed your advise. Please see the updated version of node and npm.
[root@servername UI]# node -v
v10.16.3
[root@servername UI]# npm -v
6.9.0
[root@servername UI]#

I then deleted my local Git UI repository and re-cloned it.
Upon building the project I encountered the same issue.
[root@servername UI]# mvn clean install
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.capitalone.dashboard:hygieia-ui:pom:1.0.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for org.jacoco:jacoco-maven-plugin is missing. @ line 34, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ----------------< com.capitalone.dashboard:hygieia-ui >-----------------
[INFO] Building com.capitalone.dashboard:hygieia-ui 1.0.0-SNAPSHOT
.
.
.
[INFO] --- frontend-maven-plugin:0.0.29:npm (npm install) @ hygieia-ui ---
[INFO] Found proxies: [default{protocol='https', host='proxy-server', port=<proxy port>, with username/passport authentication}, optional{protocol='http', host='<proxy server>', port=<proxy port>, with username/passport authentication}]
[INFO] Running 'npm install --https-proxy=http://<my-proxy user>:***@<proxy-server>:<proxy-port> --proxy=http://<my-proxy user>:***@<proxy-server>:<proxy-port>' in /root/hygieia/UI
[INFO]
[INFO] ><EMAIL_ADDRESS>postinstall /root/hygieia/UI/node_modules/@angular/cli
[INFO] > node ./bin/postinstall/script.js
[INFO]
[ERROR] internal/modules/cjs/loader.js:638
[ERROR]     throw err;
[ERROR]     ^
[ERROR]
[ERROR] Error: Cannot find module<EMAIL_ADDRESS>[ERROR]     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
[ERROR]     at Function.Module._load (internal/modules/cjs/loader.js:562:25)
[ERROR]     at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
[ERROR]     at startup (internal/bootstrap/node.js:283:19)
[ERROR]     at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>- 3 but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
[ERROR] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
[ERROR]
[ERROR] npm ERR! code ELIFECYCLE
[ERROR] npm ERR! errno 1
[ERROR] npm ERR<EMAIL_ADDRESS>postinstall: `node ./bin/postinstall/script.js`
[ERROR] npm ERR! Exit status 1
[ERROR] npm ERR!
[ERROR] npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
[ERROR] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[ERROR]
[ERROR] npm ERR! A complete log of this run can be found in:
[ERROR] npm ERR!     /root/.npm/_logs/2019-09-13T13_52_46_030Z-debug.log
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:20 min
[INFO] Finished at: 2019-09-13T14:52:46+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.29:npm (npm install) on project hygieia-ui: Failed to run task: 'npm install --https-proxy=http://<my-proxy user>:***@<proxy-server>:<proxy-port> --proxy=http://<my-proxy user>:***@<proxy-server>:<proxy-port>' failed. (error code 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

With both the older version and newer version of npm I am ending up with the same problem. Kindly advise

@ParashmaniD the node version seems to be 10.x it should be 8.x and npm version seems to be 6.x it should be 5.x

@rvema I am using the version of node and npm as you advised.
[root@servername UI]# gulp -v
CLI version: 2.2.0
Local version: Unknown
[root@servername UI]#
[root@servername UI]# npm -v
6.4.1
[root@servername UI]# node -v
v8.16.1
[root@servername UI]#

However, I end up with the same issue. This does not look right to me.
[root@servername UI]# mvn clean install
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.capitalone.dashboard:hygieia-ui:pom:1.0.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for org.jacoco:jacoco-maven-plugin is missing. @ line 34, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ----------------< com.capitalone.dashboard:hygieia-ui >-----------------
[INFO] Building com.capitalone.dashboard:hygieia-ui 1.0.0-SNAPSHOT
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hygieia-ui ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.4:prepare-agent (default) @ hygieia-ui ---
[INFO] argLine set to -javaagent:/root/.m2/repository/org/jacoco/org.jacoco.agent/0.8.4/org.jacoco.agent-0.8.4-runtime.jar=destfile=/root/hygieia/UI/target/jacoco.exec
[INFO]
[INFO] --- frontend-maven-plugin:0.0.29:install-node-and-npm (install node and npm) @ hygieia-ui ---
[INFO] Found proxies: [default{protocol='https', host='<proxy_server>', port=<proxy_port>, with username/passport authentication}, optional{protocol='http', host='<proxy_server>', port=<proxy_port>, with username/passport authentication}]
[INFO] Node v10.16.0 is already installed.
[INFO] NPM 6.9.0 is already installed.
[INFO]
[INFO] --- frontend-maven-plugin:0.0.29:npm (npm install) @ hygieia-ui ---
[INFO] Found proxies: [default{protocol='https', host='<proxy_server>', port=<proxy_port>, with username/passport authentication}, optional{protocol='http', host='<proxy_server>', port=<proxy_port>, with username/passport authentication}]
[INFO] Running 'npm install --https-proxy=http://<proxy_user>:***@<proxy_server>:<proxy_port> --proxy=http://<proxy_user>:***@<proxy_server>:<proxy_port>' in /root/hygieia/UI
[INFO]
[INFO] ><EMAIL_ADDRESS>postinstall /root/hygieia/UI/node_modules/@angular/cli
[INFO] > node ./bin/postinstall/script.js
[INFO]
[ERROR] module.js:550
[ERROR]     throw err;
[ERROR]     ^
[ERROR]
[ERROR] Error: Cannot find module<EMAIL_ADDRESS>[ERROR]     at Function.Module._resolveFilename (module.js:548:15)
[ERROR]     at Function.Module._load (module.js:475:25)
[ERROR]     at Function.Module.runMain (module.js:694:10)
[ERROR]     at startup (bootstrap_node.js:204:16)
[ERROR]     at bootstrap_node.js:625:3
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>- 3 but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[ERROR] npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
[ERROR] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
[ERROR]
[ERROR] npm ERR! code ELIFECYCLE
[ERROR] npm ERR! errno 1
[ERROR] npm ERR<EMAIL_ADDRESS>postinstall: `node ./bin/postinstall/script.js`
[ERROR] npm ERR! Exit status 1
[ERROR] npm ERR!
[ERROR] npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
[ERROR] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[ERROR]
[ERROR] npm ERR! A complete log of this run can be found in:
[ERROR] npm ERR!     /root/.npm/_logs/2019-09-16T10_23_49_370Z-debug.log
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  17.328 s
[INFO] Finished at: 2019-09-16T11:23:49+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.29:npm (npm install) on project hygieia-ui: Failed to run task: 'npm install --https-proxy=http://<proxy_user>:***@<proxy_server>:<proxy_port> --proxy=http://<proxy_user>:***@<proxy_server>:<proxy_port>' failed. (error code 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[root@servername UI]#

I am pointing to commit
[root@servername UI]# git log
commit d2e63ecb68aa193d355d3cfca196c05d934862f9
Merge: 208949b 9fab5eb
Author: jhoelscher7<EMAIL_ADDRESS>Date:   Thu Jul 25 16:40:38 2019 -0400

    Merge pull request #29 from jhoelscher7/gauge-chart

    Shared Gauge chart

commit 9fab5ebb9d42b245740f5615ac71379a4eb27f93
Merge: 67adc63 208949b
Author: jhoelscher7<EMAIL_ADDRESS>Date:   Thu Jul 25 16:34:39 2019 -0400

    Merge branch 'master' into gauge-chart

commit 208949bfc2b340fe08cef6c69bb1fa16835aef18
Merge: 5dbab62 cb8c436
Author: jhoelscher7<EMAIL_ADDRESS>Date:   Thu Jul 25 16:34:05 2019 -0400

    Merge pull request #31 from Hygieia/Sbrenthughes-patch-1

    Updating Readme version

It has been a few months since I started to work on this to get it up and running but it does not feel I am getting anywhere.
I am not sure if I am doing anything incorrect. Is there any sequence of action that I am missing?

we suspect presence of angular cli v8 is not liking the older version of angularjs which the current version of Hygieia UI is running on

@rvema Excellent. What is the next course of action to make this work?

@rvema , could you please provide me with the latest "working version"/commit id of all the projects and dependencies of Hygieia so that I can stand up an instance of it?

I don't quite follow this. Was the RangeError: Maximum call stack size exceeded exception issue fixed? If so, how? I am running into the same issue.
gulp -v
CLI version: 2.2.0
Local version: 3.9.1

npm -v
6.4.1

node -v
v8.16.2

Actually, I got it working now. I reset the package.json file to my last commit and it worked. I must have installed something my mistake (I think babel-core, but not sure).


Fix edit event time field

Closes #242

Codecov Report

Merging #243 (144274e) into master (fff1829) will decrease coverage by 0.04%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##             master     #243      +/-   ##
============================================
- Coverage     69.83%   69.79%   -0.05%
  Complexity      918      918
============================================
  Files           120      120
  Lines          3216     3218       +2
  Branches        438      439       +1
============================================
  Hits           2246     2246
- Misses          847      848       +1
- Partials        123      124       +1

Impacted Files
Coverage Δ

...hall/logic/parser/edit/EditEventCommandParser.java
91.30% <33.33%> (-8.70%)
:arrow_down:

...eforhall/logic/commands/edit/EditEventCommand.java
92.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fff1829...144274e. Read the comment docs.


feat(markdown additions) Adding device method markdown to JSON file.

Each file has added a markdown table to highlight elements of the method.

Hi Alexander: The license/cla check hasn't completed for this PR & commit.  This is outside the control of the RDK CMF.  We don't have a record of you signing the CLA, so we can't clear the check.  Workaround: please make a small change to the commit so the check gets kicked off again.  Thank you,
Martin Hughes, RDK CMF Compliance Team

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Updating prometheus image to a new version getting revert back to original version

What did you do?
How to update the prometheus image from v2.0 to v2.2 without deleting the statefulset? I tried changing the image from statefulset but operator will immediately revert that to original version.
What did you expect to see?
Prometheus v2.2 gets updated
What did you see instead? Under which circumstances?
Revert back to original prometheus v2.0
Environment

Prometheus Operator version:
0.14

Kubernetes version information:
v1.9.5

Kubernetes cluster kind:
kops

Manifests:
alertmanager, kube-state-metrics, node-exporter, prometheus-operator, prometheus

Prometheus Operator Logs:
N/A

How to update the prometheus image? I tried changing the image from statefulset but operator will immediately revert that to original version.

You need to change the image and or version in the Prometheus object.

Thanks @brancz.


Support for Zephyr 7B model

Hi Nvidia Team,
Please add the support for Zepyhr 7B model.
https://huggingface.co/HuggingFaceH4/zephyr-7b-alpha

Thanks for your suggestion.
Let me add it to the list of models that were requested and we will keep you posted.
Juney

Hi @TheCodeWrangler  we have not tested Zephyr so cannot comment. If you do, definitely let us know!

I am hoping to understand what makes a new arch. work/not work with tensorRT-LLM to compile .engine files.

TensorRT-LLM is invariant to hyper-parameters, but not architectural changes. ie, if you want to change the number of layers or heads, that's fine, but if you want to replace GQA with SWA or layernorm with RMSnorm, that requires code changes. You can check out the args of the models you're interested in to see which hyperparams are exposed.

I have heard that the architecture of Zephyr is very similar to LLama. Does tensorRT-LLM not work currently on Zephyr?
I am hoping to understand what makes a new arch. work/not work with tensorRT-LLM to compile .engine files.

Have you tested it?

I have tested a trained Zephyr 7b model extensively today, with no success at all.
I've used an ensemble repository, debugged to see the in- and outputs, however, the generated TensorRT engine doesn't seem to respond when fed the input tokens from the preprocessor/tokenizer.
This I have tested with 2 way Tensor parallelism + 2 way pipeline parallelism, 2 way Tensor parallelism and no parallelism at all, all running on a DGX.
The Engine does actually respond when querying it with the run.py script, which does strike me as odd, so I may have an issue with the actual model setup, so further investigation may be required.

After another round of testing today, the same engine suddenly does seem to work, to the point where I can't replicate the empty response anymore... So I guess there is at least some level of compatibility?

As more and more new models enter the market, we have prepared comprehensive instructions for TRT-LLM developers on adapting to new models of interest. We encourage our community developers to expand the range of supported models, fostering an open ecosystem with rapid iterations.
Please try following these instructions and let us know if you encounter any issues during the adaptation process. We greatly appreciate your dedication.

@laikhtewari


mruby support

First of all, this is really an awesome project. Congratulations.
I'd like to add support to mruby. Afaik I need to change config.go to add support for a new platform and create a docker container to generate the binary runtime for lambda.
Could you open the tjholowaychuk/up-crystal docker file in a way the community could implement new languages?
Thanks in advance.

Thanks! I'm actually not sure where I put that Dockerfile, but so long as we can output a binary the implementation isn't too important.
I briefly looked at adding regular Ruby support, but I had some trouble getting the gems to be placed in such a way that it could find them. That might be the more awkward part, but happy to help if I can!

Leaving this here in the extremely unlikely chance you haven't seen it: https://aws.amazon.com/blogs/compute/scripting-languages-for-aws-lambda-running-php-ruby-and-go/
With it, I was able to setup a (mostly) functional fn for testing analytics-ruby, so I assume Up could do the same

@tj what is the spec of the binary? I mean the input/output, binary name, exit codes and so on. Would be great if you can give me a brief guidance about how to implement a new runtime from scratch.
I'm thinking about two approaches.
The first one is using mruby that can output a binary with embedded gems like crystal lang: https://github.com/mruby/mruby
The second is using full ruby with Sinatra gem, for example: https://github.com/sheakelly/serverless-ruby-sinatra-example
For full ruby, the easiest approach would be traveling ruby: http://phusion.github.io/traveling-ruby
As you already did the tooling and lambda/gateway management runtime agnostic, I think couldn't be that hard to implement mruby and ruby.

@luisbebop I'll try and doc soon, but basically by default it expects an executable named ./server to run on PORT, that's about it. Currently it's not very modular, they're just little config tweaks inferred from the files present.
Outputting a single binary with the gems would be awesome! If there's no real downside to that performance-wise that sounds great to me.
We could later have "runtime": "mruby" if both end up being supported.

Won't this work just fine if there's a bash script called ./server that just started a regular server? Doesn't up already zip up the folder and deploy the whole thing? If yes, then the only thing left would be to vendor the gems during a bundle install.

@sudhirj yep that sounds like it should be fine, if the gems can be safely symlinked that should be plenty fast enough too I hope

Yeah, just doing bundle install --deployment prepares the current folder to run a deployed zip without any further ado. Think that's what Heroku does as well, when they make the slug zips that they deploy.
Put another way, up could theoretically support deploying the output of any Heroku buildpack, assuming it was built in the correct environment and had the web section of the Procfile running as just ./server

If up were to parse procfiles and use the web section command, then it's actually possible to just assert that up can run the output of any Heroku buildpack and piggyback on that ecosystem. The PORT requirement is already in play there.

sweet yea that would be great, I'll have to read up more on what they're doing I'm vaguely familiar with the buildpacks but I don't know if it'd be hard to run them in Lambda or not

Using Traveling ruby is possible to deploy ruby applications without changing anything on Up.
Check it out:
https://github.com/luisbebop/sinatra-up-demo

Mruby up and running on Up
https://github.com/luisbebop/mruby-app-up
Got 22k req/s with this little app :)
AWESOME

Niceeee :D


fixed demo for cross-browser, OS support, with Safari/iOS focus.

This demo doesn't work on Mac Safari and all iOS browsers. After these adjustments, it is working fine on all browsers.

we have inserted the fix in another PR
thanks for the feedback @mukeshMukesh12

we have inserted the fix in another PR
thanks for the feedback @mukeshMukesh12

Thanks @benyael15


Generate more meaningful stack traces with source mapping

We concatenate our source code with Webpack, making line numbers in stack traces less meaningful, e.g.,
TypeError: Cannot read property 'words' of null
  at Object._doReset (/private/var/folders/9y/jgtj1b7n6mz2_rtg61cvdb140000gn/T/AppTranslocation/610C7176-3827-4A84-AAD2-D00C52F8CC9F/d/Cosmos%20Voyager.app/Contents/Resources/app/dist/renderer.js:107634:33)
  at Object.reset (/private/var/folders/9y/jgtj1b7n6mz2_rtg61cvdb140000gn/T/AppTranslocation/610C7176-3827-4A84-AAD2-D00C52F8CC9F/d/Cosmos%20Voyager.app/Contents/Resources/app/dist/renderer.js:7434:19)
  at Object.reset (/private/var/folders/9y/jgtj1b7n6mz2_rtg61cvdb140000gn/T/AppTranslocation/610C7176-3827-4A84-AAD2-D00C52F8CC9F/d/Cosmos%20Voyager.app/Contents/Resources/app/dist/renderer.js:7772:27)
  at Object.init (/private/var/folders/9y/jgtj1b7n6mz2_rtg61cvdb140000gn/T/AppTranslocation/610C7176-3827-4A84-AAD2-D00C52F8CC9F/d/Cosmos%20Voyager.app/Contents/Resources/app/dist/renderer.js:7419:19)
  at Object.subtype.init (/private/var/folders/9y/jgtj1b7n6mz2_rtg61cvdb140000gn/T/AppTranslocation/610C7176-3827-4A84-AAD2-D00C52F8CC9F/d/Cosmos%20Voyager.app/Contents/Resources/app/dist/renderer.js:6194:46)
...
(9 additional frame(s) were not displayed)

Use source mapping so that we can see the line numbers in the original source code.

Scope:

[ ] enable sourcemaps in webpack
[ ] check that errors in chrome use sourcemaps
[ ] bonus: check that errors in sentry use sourcemaps

Another possibility to explore is whether we can get Webpack to stop concatenating the files.


allow room creation to be overridden

useful for cleanly using sub-classes of Room

Nice one, thanks @amitport! Just released 0.9.13 with it. Cheers!


Fix all Build Warnings

[X] Validate SSH Attach To Process
[X] Validate Docker Attach to Process
[X] Validate WSL Attach to Process
[X] Validate Output Window Logs

@gregg-miskelly Any other scenarios to double check to see if it throws if its not on UI thread?

@gregg-miskelly Any other scenarios to double check to see if it throws if its not on UI thread?

Do you mean besides SSH/Docker attaches? If so: nope, that is the only thing I was worried about.

Yep. C++ and C# SSH/Docker/WSL don't throw any errors.
Tested via F5 MIDebugPackage with the MIDebugPackage.dll, SSHDebugPS.dll modules loaded and hit breakpoints to double verify.

:shipit:


Crashed upon running missions

Is anyone facing the same issue with v1.0.37 release? How do i go around to fix it?
Thanks!

#52

@HotMoogle thank you... my apologies for asking dumb questions here, but how do i go about updating that figure? do i need Visual Studio to update any .cs?
Also, if you happen to have a working folder, do you mind sharing them with me to my email<EMAIL_ADDRESS>Thank you so much!

download VS 2017 community edition. open solution
update which is indicated above! this thread :)

@HotMoogle thank you! I updated the networking.cs, app, rsc and mst, then ran without debugging and overwrote the existing .dll in the program folder with the newly compiled .dll
However I managed to get to GetUserInfo - Request Done and still crash there. Any idea how i can fix this?


Add a size cap for boxes

fixes #479

👍 Looks good. I'd like to do something about error descriptions, but after our discussion, that sounds like it would probably be a different PR.


fix: use alpine base, update go1.22

fixes https://github.com/raffis/renovate-metrics/issues/28

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

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

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
0

Relevant Lines:
211

💛  - Coveralls


JAXB integration tests failing fix if locale different from EN #4135

@zbendhiba Please review this, and please do let me know for further improvements.


basic_headers, Headers to become basic_fields, Fields (API Change)

Now that we have message_headers to refer to a HTTP message without the body, the term "headers" has become ambiguous. Specifically class basic_headers, and the Headers template argument name can be confused with message_headers. I am strongly considering the following changes:

Define "fields" to mean to a collection of HTTP field name / value pairs
Define "headers" to mean a container holding "fields" plus the request or response line specific items (method, uri, status code, and reason phrase)
Rename class template basic_headers to basic_fields
Rename class template alias headers to fields
Rename Headers in template parameter lists to Fields
Rename message_headers to just headers
Rename message_headers::headers to headers::fields
Change documentation to be consistent with these terms

This is a fairly big API change and I'm interested in hearing from any/all stakeholders with feedback.

Synopsis of proposed changes
/// A container for HTTP request or response headers
template<bool isRequest, class Fields>
struct headers
{
    ...
    using fields_type = Fields;
    fields_type fields;
};

/// A container for a complete HTTP message
template<bool isRequest, class Body, class Fields>
struct message : headers<isRequest, Fields>
{
    ...
};

/// A container for HTTP field value pairs
template<class Allocator>
class basic_fields;

/// A typical HTTP field value pair container
using fields = basic_fields<std::allocator<char>>;

/// Serialize HTTP/1 message to a SyncWriteStream
template<class SyncWriteStream, class DynamicBuffer,
    bool isRequest, class Body, class Fields>
void
write(SyncWriteStream& stream, DynamicBuffer& dynabuf,
    message<isRequest, Body, Fields> const& m);

My 2 cents.
What you intend to name "fields", RFC names "headers". So I suppose it will be confusing too.
I name (in my library) request/response without body - "request_head" and "response_head". Not so pretty names but not ambiguous and short .

Yeah these changes are not perfect, but I believe they are a step in the right direction. Currently we have message_headers, headers, message_headers::headers, and message::headers. Clearly, something needs to change :-)

IMHO, the only thing a bit awkward is that you have a single headers object that contains multiple fields.  Can a message have more than one headers? If not, perhaps call that struct header instead.

+1 this fits well with the documented field concept
https://vinniefalco.github.io/beast/beast/ref/Field.html
I agree with @bachase that header (instead of headers) should be considered.

Clearly, something needs to change :-)

Undoubtedly :-)


Build fails when using EME

The build fails when using b9ddc533754fb33b4043cac1734730313ce74c7c or newer of shaka-player-embedded and 28c44ac of prebuilt_cdm (latest master) with the following error:
...
In file included from ../shaka/src/mapping/backing_object.h:23:
../shaka/src/mapping/weak_js_ptr.h:114:34: warning: unused parameter 'tracer' [-Wunused-parameter]
  void Trace(memory::HeapTracer* tracer) const override {
                                 ^
../prebuilt_cdm/shaka_plugin/cdm_host.cc:31:7: error: use of undeclared identifier 'PlainCallbackTask'
      PlainCallbackTask(std::bind(&IClient::onTimerExpired, client, context)));
      ^
In file included from ../prebuilt_cdm/shaka_plugin/cdm_host.cc:3:
In file included from ../prebuilt_cdm/shaka_plugin/cdm_host.h:11:
...
10 warnings and 1 error generated.
[728/1042] CXX obj/internal_sources/environment.o
ninja: build stopped: subcommand failed.

Build without EME seems okay
The whole log here: spe_build_error.txt

Configuration command:
../configure --ios --cpu arm64 --eme-impl ~/XcodeProjects/prebuilt_cdm/shaka_plugin/dev_cdm.json

macOS 10.15.4
Xcode 11.4.1

I really need to include EME in our pre-submit checks.  I forgot to update the CDM plugin with some recent changes.

I just pushed a fix to the prebuilt_cdm repo.  Also, I've updated our pre-submit checks so hopefully I won't break EME plugins again.


Mention CRD install for system-upgrade-controller

Addresses: https://github.com/rancher/rke2-docs/issues/222
Signed-off-by: Derek Nola<EMAIL_ADDRESS>

There is one caveat if we follow these steps, there are two resources (role and rolebinding) that fail to be created because the namespace was not yet created. The namespace gets created in system-upgrade-controller.yaml too but I guess it is not there yet when needed
 Error from server (NotFound): error when creating "https://github.com/rancher/system-upgrade-controller/releases/latest/download/system-upgrade-controller.yaml": namespaces "system-upgrade" not found
Error from server (NotFound): error when creating "https://github.com/rancher/system-upgrade-controller/releases/latest/download/system-upgrade-controller.yaml": namespaces "system-upgrade" not found

If I apply system-upgrade-controller.yaml again, it works. Maybe we should warn users about it?

I have been meaning to get a bit more hands-on with that repo; I allowed some folks to make changes to the deployment manifests that in retrospect only work well when using kustomize, and have made things a bit more painful if just using kubectl apply as we suggest in other repos docs.

Agree, I think the user experience is now worse than in 0.13.2

Regardless of making SUC better, this does fix the upgrade docs to at least work.


Links get corrupted

Describe the bug
Certain kind of link gets corrupted/misformatted bridging slack (new bot variant) to matrix.
Specifically one of the double dashes (minus signs) gets deleted and the link will only be formatted until the character before the dashes. Link is fine inside slack (website).
To Reproduce
Send a onedrive share link from slack to matrix.
Expected behavior
Working link formatting
Screenshots/debug logs

{
  "type": "m.room.message",
  "sender": "@matterbridge:myserver.tld",
  "content": {
    "msgtype": "m.text",
    "body": "[slack] <Max> https://1drv.ms/w/s!Anfsv--MQXXXXXXXXXXXXXHi1",
    "format": "org.matrix.custom.html",
    "formatted_body": "[slack] <Max> https://1drv.ms/w/s!Anfsv–MQXXXXXXXXXXXXHi1"
  },
  "origin_server_ts":<PHONE_NUMBER>877,
  "unsigned": {
    "age": 3716119
  }
}

Environment (please complete the following information):

OS: Debian GNU/Linux 9.11 (stretch) (GNU/Linux 4.19.0-0.bpo.5-amd64 x86_64 )
Matterbridge version: version: 1.15.1 87788f3

Additional context
[matrix.myserver]
Server="https://myserver.tld"
Login="matterbridge"
Password=
RemoteNickFormat="[{PROTOCOL}] <{NICK}> "
NoHomeServerSuffix=true

[slack.server]
Token="xoxb-"
RemoteNickFormat="{NICK}"

[[gateway]]
name="gateway"
enable=true

[[gateway.inout]]
account="slack.server"
channel="channel"

[[gateway.inout]]
account="matrix.myserver"
channel="#room:myserver.tld"

Evidence points to this lib introducing this bug:
https://gitlab.com/golang-commonmark/linkify/issues/1

Hey, HarHarLinks asked me about the issue previously and he asked me to give my 2cents.
I looked into the problem and identified that the problem probably lies in linkify. The parser does not parse according to the url spec.
The URL parser in linkify looks very different to the sample parser given by https://url.spec.whatwg.org/#concept-basic-url-parser
I am not sure how many projects use that commonmark parser. But it seems not too many use it and/or there is not a lot of activity on the repositories.
Maybe consider switching to https://github.com/gomarkdown/markdown for example if there is no activity on the gitlab issue in the near future.
According to the maintainer, they even used a fuzzer to find bugs in the parser (https://blog.kowalczyk.info/article/n/fuzzing-markdown-parser-written-in-go.html) which is a huge pro when considering different markdown parsers.

The maintainer of linkify "solved" the issue, so this issue might not appear in future builds. However this doesn't seem very well designed and I agree that you should maybe take a look at the lib proposed by valkum.

Hi @HarHarLinks and @valkum thanks a lot for reporting the issue, debugging it and reporting the fix. Much appreciated 👍
I've updated the vendor from upstream. This should fix the issue in master. You can download dev binaries or rebuild it yourself. A 1.16.1 containing this fix will also be released soon.
I'll open a new issue for using https://github.com/gomarkdown/markdown (seems to be a better version than the blackfriday one matterbridge was using before switching to the current one)


[BUG] splash not working with latest manifest

I just noticed that splash does not seem to work with downloading latest manifest ig version 17.30 due to it being like smaller/binary.
this is the error when trying to read it
invalid character '\f' looking for beginning of value
read this https://github.com/EpicGames/UnrealEngine/blob/master/Engine/Source/Runtime/Online/BuildPatchServices/Private/Data/ManifestData.cpp#L561

@3ldor this is a major bug for this program since it can't read latest manifests

Um is this program never getting updated anymore?

sadly
Failed to fetch manifest: invalid character '\f' looking for beginning of value

ah it might work again some time


Condition elevations in the camera pose

Great work! I am curious about the camera_embedding in simple_image_dataset.py, in your code base, the camera embedding also includes elevations_cond,
camera_embeddings = torch.stack([elevations_cond, elevations, azimuths], dim=-1) # (Nv, 3)
and based on the code about elevations_cond
elevations_cond = torch.as_tensor([0] * self.num_views).float()
it seems that the elevations_cond is always 0, why do you choose to add this variable to the camera_embedding? I am just a little curious about it, it seems that without this variable is also ok.
Thanks for your reply soon!

Yes.  The evevation degrees should be all zero. However,  due to a bug, I use wrong cameras poses (in the current repo) to train the model. But since the camera poses are fixed for all objects in the training, the wrong camera poses won't affect the final results.


Add MTGRennes

Add MTG Rennes (FRANCE) community thx for the review

@YoannGUILLO just left some comments on the data.json file. Can you review it?

@YoannGUILLO thanks! Merged.

Comments removed.


what do when internet connection is lost

Do the library manage automatically the lost of internet connection?
It tries to reconnect or i have to manage this situation?
Thanks

Thanks for your question!
There's some support for this situation built-in already:

It should try to re-connect automatically (here). There's an open issue regarding this feature: https://github.com/delight-im/Android-DDP/issues/62
It should queue all messages that couldn't be sent to the server yet and wait for the connection to be established again, then send everything (here). There's an open issue regarding this feature: https://github.com/delight-im/Android-DDP/issues/61

As you see, this should really be handled by this library, it shouldn't be your task to do this. If things are not working as expected yet, let's fix and improve them.


Update Windows Terminal to v1.12.10732

This update to Windows Termainl has a fix for the issue "Element not found" affecting a number of scoop users:
https://github.com/microsoft/terminal/issues/12305

/verify

/verify

Thanks a lot to the maintainers for all your care.
I double confirm that this works on Windows 10 and on Windows 11.


Add team and robot icons

For use in Nebula workspaces and future account pages:

@joeclayallday or @zhen0 has the svgs!

Now's my time to shine — voila!
Team & Robot Icons.zip


stock_layout_iteration and hot reload regressions

Since rolling Flutter's engine to include the Dart roll from 69817eea182384b40ef658d578fd49cac00c5874 to 21eddc429e9c7260de00a9af7cad94baba830f59, the microbenchmarks stock_layout_iteration benchmark has regressed by 2x and the hot reload benchmarks have regressed by about 20% (eyeballing the chart).

@a-siva @alexmarkov Is this due to the same cause as https://github.com/dart-lang/sdk/issues/30371#issuecomment-321087982 ?

It looks like the stock_layout_iteration regression is different from #30371, as it appears during the next engine rollout. Also, it seems like it is fixed by now as the stock_layout_iteration benchmark is back to normal.

closing as fixed.


do a google colab version

ai-models is not designed for colab, but you can always try the following

from ai_models.model import load_model

kwargs = {} # Fill dict with the values of the command line arguments if needed

m = load_model("panguweather", **kwargs)
m.run()


No normal identification of EOF symbols

VSCode Version:1.20.1
OS Version:win10 64bit

Steps to Reproduce:

Create a new shell script file.
Enter the following test code:

#!/bin/bash
cat > test_file << 'EOF'
#!/bin/bash
echo "test"
if [ -f "test_file" ] ; then
    echo "yes"
else
    echo "no"
fi
EOF
echo "This a test code."

The editor does not normally identify the EOF terminator that causes subsequent incorrectly coloring of the code.

Does this issue occur when all extensions are disabled?: No

Please provide the steps for how to reproduce this issue in English.

This got fixed by the latest update of the grammar (https://github.com/atom/language-shellscript/pull/105)


Bai 16

Hi,
Your homework 15 has been reviewed, thank you for your effort.
Great! Keep up the good work!
Best wishes from Automation Test Pro,
Khanh


Remove publication templates

https://trello.com/c/kfyYY4tf/73-9-publications-migration-final-tasks-deploy-2-05-days
The rendering of these pages is now handled by government-frontend. This work removes this code from Whitehall and re-works some of the tests to equivalently test the things where assertions were previously made against these views.
It's probably easiest to review this commit-by-commit and read the commit messages.
The supersedes https://github.com/alphagov/whitehall/pull/3136 which deleted more code than was necessary.

🎉
Nice

Just the one thing I've found that could also be removed.
:+1: :100:

Deployed to integration. Everything looks ok. Merging.


[music3] add a pop-up to validate exit

Commit: https://github.com/medInria/medInria-public/commit/77a42ed719e0bb8c67f159e2cad3d5eae7f53455
Original PR: https://github.com/Inria-Asclepios/medInria-public/pull/507
If the user clicks on one of the exit buttons, a message dialog is displayed to validate the exit. If the database has temporary data, the classic medSaveModifiedDialog pop-up is displayed instead.
:m:

This PR has been rebased


Missing mapping for PS4 touchpad button and possibly others like XboxOne elite paddles

Godot version
3.4.stable
System information
Windows 10
Issue description
Mapping for some extra buttons like PS4 touchpad are missing on Windows. The touchpad field is missing from the SDL_GameControllerDB entries. After reporting the issue https://github.com/gabomdq/SDL_GameControllerDB/issues/520 I was informed that the SDL are adding those fields on its own.
Proposed solution was to add missing entry on per-GUID basis, however that leads to a problem: with the SDL controller map program omitting binding for the touchpad field entirely and some other fields missing from DB like paddles for XboxOne Elite those will be constantly overwritten. So more permament solution needs to be adapted, like creating Godot specific mapping.
Steps to reproduce

Run Godot 3.4
Download and run official Joypad demo https://godotengine.org/asset-library/asset/140
Connect PS4 controller using USB (my PS4 pad has a GUID: 030000004c050000cc09000000000000)
Press the touchpad button, notice nothing happened
Press the "Set Raw Mapping" and press touchpad again
Notice button 13 is being marked as pressed

Minimal reproduction project
Official joypad demo: https://godotengine.org/asset-library/asset/140

This needs to be fixed upstream.
Note: Despite the suggestion in https://github.com/gabomdq/SDL_GameControllerDB/issues/520 that this should be fixed in Godot, this was fixed upstream for another PS4 controller with GUID 030000004c050000c405000000000000 in https://github.com/gabomdq/SDL_GameControllerDB/commit/ce357c24885d9d22e4a70307ec462a1b9a7145aa, which was obtained from its upstream https://github.com/libsdl-org/SDL/commit/b6bc3a6b0e435eae7340acc5d51ec05d7f21505e. This change for the other PS4 GUID was included in #55781, which was cherry-picked in 2025648d6d2ab2c3765efd483307e82f1fae3cc8 for 3.4.1.

Feel free to read the SDL source for yourself and realize that your options are either buying and testing the 40+ controllers to manually add the field, or packaging SDL’s data and setting it automatically by type.


fix(deps): update dependency io-ts to v2.2.4

This PR contains the following updates:

Package
Type
Update
Change

io-ts
dependencies
minor
2.0.1 -> 2.2.4

Release Notes

gcanti/io-ts
v2.2.4
Compare Source

Polish

remove the dependency on the either instance as a mean of improving tree shaking (@gcanti)

v2.2.3
Compare Source

Polish

use the built-in Readonly type in readonly combinator, closes #472 (@gcanti)

Experimental

split instances (@gcanti)
add Type experimental module, #464 (@gcanti)
restore the O type parameter to Encoder, #469 (@gcanti)
add the O type parameter to Codec (@gcanti)
add JsonCodec experimental module (@gcanti)
add JsonEncoder experimental module (@gcanti)
Schemable

rename Schemable interface to Schemable1 (@gcanti)
rename WithUnion interface to WithUnion1 (@gcanti)
add Schemable interface (@gcanti)
add WithUnion interface (@gcanti)
add WithRefinement / WithRefinement1 interfaces (@gcanti)
add WithUnknownContainers / WithUnknownContainers1 interfaces (@gcanti)

move UnknownArray and UnknownRecord to WithUnknownContainers (@gcanti)

Schema

refactoring with the new Schemable interface (@gcanti)
add interpreter function (@gcanti)

Internal

upgrade to<EMAIL_ADDRESS>(@gcanti)

v2.2.2
Compare Source

Experimental

add Eq module (@gcanti)
Codec

add TypeOf operator (@gcanti)

Decoder

add DecodeError interface (@gcanti)

Encoder

add TypeOf operator (@gcanti)

Guard

add TypeOf operator (@gcanti)

v2.2.1
Compare Source

Experimental

Decoder

collect all errors while decoding, closes #449 (@gcanti)

v2.2.0
Compare Source

Experimental

add Codec, Decoder, Encoder, Guard, Schema, Schemable, Tree modules (@gcanti)

v2.1.3
Compare Source

Polish

remove useless hasOwnProperty calls, closes #423 (@gcanti)

v2.1.2
Compare Source
v2.1.1
Compare Source

Bug Fix

fix record domain handling, closes #391 (@gcanti)

v2.1.0
Compare Source

New Feature

add bigint codec (@mixedCase)

v2.0.6
Compare Source

Bug Fix

whitelist window in UnknownRecord, fix #413 (@gcanti)

v2.0.5
Compare Source

Bug Fix

partial shouldn't allow arrays, fix #407 (@gcanti)

v2.0.4
Compare Source

Bug Fix

remove getters, fix #404 (@gcanti)

v2.0.3
Compare Source

Bug Fix

rewrite es6 imports (@gcanti)

v2.0.2
Compare Source

Bug Fix

fix #397 (@gcanti)

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Codecov Report

Merging #54 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #54   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           22        22
  Lines          480       480
  Branches        80        80
=========================================
  Hits           480       480

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a9118aa...d21a6c9. Read the comment docs.


HowTo: Manually resend invite

Hi all. Not issue but was wondering if there was an option for manually resend an invitation? Been looking at the controller but cannot see how to manually resend.
Do I need to create a PR for this or it's there somewhere already done?
Thanks

If a user tries to invitate an already invited user, and resend_invitation is enabled, new invitation will be sent.
Also you can get the invited user record and call invite!
In both cases, new invitation token is generated, as Devise changed to save a hash of tokens for better security, so raw token is not available to send an email with the same token.
If you want both old and new invitations to work, DeviseInvitable needs to save invitation info in a different table, so an user can have many invitations and all tokens work, as requested few times, e.g. #869 and linked issues, but I couldn't work on it before.

Thanks. I guess this would do. I'll reopen if I'm struggling but should be straight forward.


selectInput and tabPanel are confused when served by ShinyProxy

Dear all,
I have a very strange bug that occurs only when the Shiny app is served by ShinyProxy. I boiled the problem down to a minimal example.
Demonstration:

Problem description:
After changing the Input the trying to go to Tab 2, the selectInput opens again and cannot be closed.
Notes

The bug is not present when the app is started directly
The bug is not present when the app is served in a docker container directly
The bug is only present when served through ShinyProxy
The bug is present in Firefox and Chrome, but not in Opera browser
all packages are updated
The problem can be reproduced with ShinyProxy 2.6.0 to (at least) 2.3.0

I noted this in a large shinydashboard app using a shinyWidgets-airDatePicker and boiled it down to pure Shiny and selectInput.
Testing setup
The 4 files (app, dockerfile, packages, and ShinyProxy-config) needed to reproduce the problem are here: https://gist.github.com/shosaco/ff3ff16c47550e571a92b515dd4e8ba4
Steps to reproduce the problem

Build docker image for app: docker build -t test .
Start ShinyProxy (after downloading the *.jar): java -jar shinyproxy-2.6.0.jar
Navigate to http://localhost:8081
Follow the instructions: Change the Input value and go to tab 2
The selectInput stays open and cannot be closed.

Severity
Any inputs or menu items below the selectInput are inaccessible because the opened input blocks the view and click, in other words, the app itself it blocked.
Thanks in advance for your help.
Best regards
sandro

It's not an issue in private/incognito browser mode, so I suggest one of my browser plugins to be the root cause.


remove ipython and setuptools restriction

celery 5.2.4 got released (latests 5.2.6) and also ipython 8.2.0.
Tried installing with invenio-app-rdm 9.0.0.dev11 and it worked (took 2 minutes):
🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 214/214 — 00:02:27

:snake:


Question on battery

Not an issue, just a question.
In the BOM you say this for the battery
18650 Battery 3350 mAh (Not recommended!)
But I don't see any explanation anywhere for why you don't recommend it. Did you have issues? TIA

Yeah I am interested in an answer on this too...

If I remember correctly, the battery doesn't have a security circuit. Therefore I wouldn't want to recommend it. Otherwise nothing wrong with it. Works fine for me.

If I remember correctly, the battery doesn't have a security circuit. Therefore I wouldn't want to recommend it. Otherwise nothing wrong with it. Works fine for me.

That is correct. I thought that if you take an additional step, it would need the protection and probably charging circuitry. I think it is perfect as is though.
I just wanted to make sure that you didn't have one blow up on you, and we're suggesting a different brand 😁.
Thanks again for the awesome design.


fix: make it possible to embed x.com post with the embed plugin

Description
Twitter / X changed its domain from twitter.com to x.com recently, so when users click the "Copy link" button, they will get a "x.com" link, which the embed plugin can't handle.
This PR checks for x.com links and treat them as twitter.
Fixes # (issue)
https://github.com/Darginec05/Yoopta-Editor/issues/165
Type of change
Please tick the relevant option.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings

Thanks for PR @penghuili
Did you check if this API will work with x.com?
https://github.com/Darginec05/Yoopta-Editor/blob/master/packages/plugins/embed/src/providers/Twitter.tsx#L21

Thanks for PR @penghuili
Did you check if this API will work with x.com?
https://github.com/Darginec05/Yoopta-Editor/blob/master/packages/plugins/embed/src/providers/Twitter.tsx#L21

Yes, I tested it locally with a x.com link, it works.

@Darginec05 would you merge this? I don't think I have the permission.

@penghuili yeap, I'll merge PR and publish it as patch soon.
Thanks


Inquiry on Other possibility with OpenLayer

Aside from using maps with OpenLayer, would it be possible to use it with other javascript library that creates org charts?  For example, http://gojs.net/latest/samples/orgChartExtras.html.
We are hitting a wall now with displaying thousands of notes it is taking too much time.  Would OpenLayer be a solution?  Any advice is appreciated.

Please use the mailing list of an online forum instead of github issues for inquiries
https://groups.google.com/d/msg/ol3-dev/WzJ8ewR8HGI/09726Th0RE0J


The field ordering in generated cabal files is not consistent.

@fergushenderson found out that field ordering are not consistent: an example can be seen from string-conversions. In particular default-language is before build-depends in library, but after build-depends in test-suite spec.

This is by design, hpack tries to produce .cabal files with minimal diffs.  If you delete any existing .cabal file before running hpack you will get deterministic fields orders.


There is a mysterious <class 'wx._core.Window'>: {} object which is a child of ListCtrl.  Deleting that object causes the segfault.

Why was this ophan-culling code added? It's hard to tell from the commit. https://github.com/chriskiehl/re-wx/commit/40ec49fa86f381b53d82948b6c954fe7c1f2e9ee There must have been a particular Control which was creating a lot of problem orphans.


create login page

Related issue: #5
This is a draft pull request, please review it. Thank you!

Nothing to comment on, Gary has been pretty extensive. Did want to note the Material 3 issue found on stack overflow, but otherwise everything is on track here by my eye.

Thank you for your feedback. I have been actively working on implementing it.

This looks great! It's working on end as well, I'm able to enter email and password. Just echoing from the comments above but comments would helpful for clarity. Certain TODO's as well could show what the next steps are. That login composable function seems big, could probably break it up into smaller helper functions. Other than that it looks good.

Hi everyone, I will close this pull request and this PR   #8  will handle the issue.


WebpackError: Cannot read property 'node' of undefined

Anyone run into this when trying to run a build?
error Building static HTML for pages failed
See our docs page on debugging HTML builds for help https://goo.gl/yL9lND
  58 |         ? this.props.data.allAuthorsJson.edges
  59 |         : [];
> 60 |     const getAuthor = () => authorsEdges[0].node;
     |                                             ^
  61 |
  62 |     return (
  63 |       <Drawer className="author-template" isOpen={this.state.menuOpen}>

  WebpackError: Cannot read property 'node' of undefined

   - author.jsx:60 getAuthor
     src/templates/author.jsx:60:45

   - author.jsx:78 AuthorTemplate.render
     src/templates/author.jsx:78:34

   - ReactCompositeComponent.js:796 ReactCompositeComponentWrapper._renderValidatedComponentWithoutO    wnerOrContext
~/react-dom/lib/ReactCompositeComponent.js:796:1

   - ReactCompositeComponent.js:819 ReactCompositeComponentWrapper._renderValidatedComponent
~/react-dom/lib/ReactCompositeComponent.js:819:1

   - ReactCompositeComponent.js:359 ReactCompositeComponentWrapper.performInitialMount
~/react-dom/lib/ReactCompositeComponent.js:359:1

   - ReactCompositeComponent.js:255 ReactCompositeComponentWrapper.mountComponent
~/react-dom/lib/ReactCompositeComponent.js:255:1

   - ReactReconciler.js:43 Object.mountComponent
~/react-dom/lib/ReactReconciler.js:43:1

   - ReactMultiChild.js:234 ReactDOMComponent.mountChildren
~/react-dom/lib/ReactMultiChild.js:234:1

   - ReactDOMComponent.js:657 ReactDOMComponent._createContentMarkup
~/react-dom/lib/ReactDOMComponent.js:657:1

   - ReactDOMComponent.js:524 ReactDOMComponent.mountComponent
~/react-dom/lib/ReactDOMComponent.js:524:1

Unfortunately, that error message is miss-leading, this is the actual error.
> 60 |     const getAuthor = () => authorsEdges[0].node;
It looks like you are running into an issue where the site cannot find the default author. Currently, you need to have at least 1 author file in the author folder. The author code is pretty fragile and needs to be revisited as well as the folder structure.  Right now you might need a path like this: content/authors/authors/casper.json.
Check the blogAuthorDir value in your data/SiteConfig.js file. The author filename might need to perfectly match the ID, but I'll have to double check.  The 'author' value in a blog post has to match the AuthorID perfectly.
Author filename example for 'casper' user:
casper.json
Expected formatting for an author json file:
{
  "id": "casper",
  "name": "Casper User",
  "image": "https://api.adorable.io/avatars/150/test.png",
  "url": "http://gatsbyjs.org/",
  "location": "North Pole, Earth",
  "bio": "Yeah, I like animals better than people sometimes... Especially dogs. Dogs are the best. Every time you come home, they act like they haven't seen you in a year. And the good thing about dogs... is they got different dogs for different people.",
  "socialUrls": [
    "https://github.com/gatsbyjs",
    "https://twitter.com/gatsbyjs",
<EMAIL_ADDRESS>  ]
}

@antonioOrtiz Feel free to re-open this issue if you are still running into trouble.

Hi Everyone, I got the following error message while running the gatsby build command for the first time.

However, gatsby develop command works fine. Could you please help me on this  :blush:.

Hi Everyone, I got the following error message while running the gatsby build command for the first time.

However, gatsby develop command works fine. Could you please help me on this 😊.

Hi @haysclark after adding nodes in pageContex property in tag.jsx issue is fixed now. Like this
pageContext: { nodes, tag, page, pages, total, limit, prev, next }
But still there is the cannot find module '!raw-loader' warning is still there.


Path can not be used when generating Svelte-App

Actual:
Error when generating an svelte-app with a full path, e.g. nx g @nxext/svelte:app products/ui.
Error-message is Cannot read property 'architect' of undefined
Expected:
like in other existing nx-plugins would be creating the app with name products-ui inside of folder apps/products. This would make structuring the monorepo a lot easier, e.g. when building micro-apps with one folder for the api-microservice and the other with the svelte-microfrontend

New release


more information about protobuf

Refer to #908.
@wxchan Please create the README file into proto folder and give a brief guide for installing and using protobuf.

@StrikerRUS there is not much to say. I add some guide here https://github.com/Microsoft/LightGBM/blob/master/docs/Installation-Guide.rst#protobuf-support.


Settings menu unclickable in mobile

Current Behavior:
Clicking the settings icon in the Svelte or Web Components default layout with size="sm" opens the settings menu to the bottom of viewport and the menu options can't be clicked because the menu closes with every click.
Expected Behavior:
React default layout works as expected https://stackblitz.com/edit/vidstack-examples-jv627c
Steps To Reproduce:

Go to https://stackblitz.com/edit/vidstack-examples-wn3zz2
Resize preview until layout has attribute size="sm"
Click settings and try to click a menu option such as speed or captions

Yes, I noticed that too. This happens because pointer-events: none;
Can be seen on the demo page: https://www.vidstack.io/docs/wc/player/components/layouts/default-layout?styling=default-theme

Same thing on the desktop. When data-resizing is set, settings is not clickable.

Sorry everyone, I stuffed up some code and I was away for a bit helping family with renovations. Fixed and rolling it out today.


setSelected is called on the initial mounting of component

Hello there,
When this component is initially mounted the setSelected function is executed. Is this how it is supposed to behave?
I believe the setSelected function should only execute whenever the user selects a new option from the dropdown since this function is currently the only way to get the selected value. Having it run on mount leads to some nasty bugs.
Thank you!

Please let me know your package version

"react-native-dropdown-select-list": "^2.0.2

I'm seeing this behaviour also.
"react-native-dropdown-select-list": "^2.0.4"

In this section:
React.useEffect(() => {
        if(!_firstRender && defaultOption && oldOption.current != defaultOption.key ){
            // oldOption.current != null
            oldOption.current = defaultOption.key
            setSelected(defaultOption.key);
            setSelectedVal(defaultOption.value);
        }
        if(defaultOption && _firstRender && defaultOption.key != undefined){
            oldOption.current = defaultOption.key
            setSelected(defaultOption.key);
            setSelectedVal(defaultOption.value);
        }
    },[defaultOption])

I think you should remove the call to setSelected. They are not respecting the save property either.

thank RadAd this fixed the issue

Has been fixed in new version, please wait for update


filelight: Update to version 22.12.3 and fix autoupdate

Closes #XXXX

Relates to #XXXX

[X] I have read the Contributing Guide.

/verify