text:
[Bug]: Netlify Gatsby plugin causes build failures on Gatsby 2.x site

Summary
I see that you have left the 1.0.3 version of the netlify gatsby plugin accessible to older Gatsby sites, per plugins.json.
But I think you set this version exception too low, and the exception should instead be "gatsby": "<3.0.0", per this PR.
I noticed this because my v2 gatsby site that has been building fine for a few years started failing today.
Steps to reproduce
Try building a gatsby site < v3 (the screenshot is for gatsby 2.23.14)

A link to a reproduction repository
No response
Plugin version
3.5.1
More information about your build

[ ] I am building using the CLI
[ ] I am building using file-based configuration (netlify.toml)

What OS are you using?
None
Your netlify.toml file
No response
Configuration
No response
Environment
No response
Gatsby info
gatsby 2.23.14
Your _redirects file
No response
Builds logs (or link to your logs)
https://app.netlify.com/teams/emcwebmaster71/builds/63dc673f2281a7737627e527
Function logs
No response

I had a similar issue. Netlify deployments were broken.
Gatsby version: 2.24.91
Solved it by installing @gatsbyjs/reach-router
yarn add @gatsbyjs/reach-router

Yep, my build is broken as well.
Here's the entire log:
8:47:14 AM: build-image version: f40c5967c3e09a056e8b79397ce4f1c76d0df777 (focal) 8:47:14 AM: buildbot version: f40c5967c3e09a056e8b79397ce4f1c76d0df777 8:47:15 AM: Fetching cached dependencies 8:47:15 AM: Starting to download cache of 180.2MB 8:47:17 AM: Finished downloading cache in 2.154s 8:47:17 AM: Starting to extract cache 8:47:20 AM: Finished extracting cache in 2.953s 8:47:20 AM: Finished fetching cache in 5.152s 8:47:20 AM: Starting to prepare the repo for build 8:47:20 AM: Preparing Git Reference refs/heads/master 8:47:20 AM: Parsing package.json dependencies 8:47:22 AM: Starting build script 8:47:22 AM: Installing dependencies 8:47:22 AM: Python version set to 2.7 8:47:22 AM: Started restoring cached Node.js version 8:47:23 AM: Finished restoring cached Node.js version 8:47:23 AM: Attempting Node.js version 'v14.15.1' from .nvmrc 8:47:23 AM: v14.15.1 is already installed. 8:47:24 AM: Now using node v14.15.1 (npm v6.14.8) 8:47:24 AM: Started restoring cached build plugins 8:47:24 AM: Finished restoring cached build plugins 8:47:24 AM: Attempting Ruby version 2.6.2, read from environment 8:47:24 AM: Started restoring cached Ruby version 8:47:24 AM: Finished restoring cached Ruby version 8:47:24 AM: Using Ruby version 2.6.2 8:47:25 AM: Using PHP version 8.0 8:47:25 AM: Started restoring cached corepack dependencies 8:47:25 AM: mv: cannot move '/opt/build/cache/.node/corepack' to '/opt/buildhome/.node/corepack': No such file or directory 8:47:25 AM: Finished restoring cached corepack dependencies 8:47:25 AM: No npm workspaces detected 8:47:25 AM: Started restoring cached node modules 8:47:25 AM: Finished restoring cached node modules 8:47:25 AM: Bypassing sha validation. Running pre & post install scripts 8:47:25 AM: Installing npm packages using npm version 6.14.8 8:47:42 AM: npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 8:47:42 AM: npm WARN deprecated har-validator@5.1.5: this library is no longer supported 8:47:47 AM: > sharp@0.23.4 install /opt/build/repo/node_modules/sharp 8:47:47 AM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy) 8:47:49 AM: info sharp Detected globally-installed libvips v8.9.1 8:47:49 AM: info sharp Building from source via node-gyp 8:47:52 AM: make: Entering directory '/opt/build/repo/node_modules/sharp/build' 8:47:52 AM:   TOUCH Release/obj.target/libvips-cpp.stamp 8:47:52 AM:   CXX(target) Release/obj.target/sharp/src/common.o 8:47:54 AM:   CXX(target) Release/obj.target/sharp/src/metadata.o 8:47:55 AM:   CXX(target) Release/obj.target/sharp/src/stats.o 8:47:57 AM:   CXX(target) Release/obj.target/sharp/src/operations.o 8:47:58 AM:   CXX(target) Release/obj.target/sharp/src/pipeline.o 8:48:01 AM:   CXX(target) Release/obj.target/sharp/src/sharp.o 8:48:02 AM:   CXX(target) Release/obj.target/sharp/src/utilities.o 8:48:03 AM:   SOLINK_MODULE(target) Release/obj.target/sharp.node 8:48:03 AM:   COPY Release/sharp.node 8:48:03 AM: make: Leaving directory '/opt/build/repo/node_modules/sharp/build' 8:48:05 AM: npm WARN babel-preset-gatsby@0.9.0 requires a peer of core-js@^3.0.0 but none is installed. You must install peer dependencies yourself. 8:48:05 AM: npm WARN ts-node@9.1.1 requires a peer of typescript@>=2.7 but none is installed. You must install peer dependencies yourself. 8:48:05 AM: npm WARN tsutils@3.17.1 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself. 8:48:05 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/chokidar/node_modules/fsevents): 8:48:05 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 8:48:05 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/watchpack/node_modules/fsevents): 8:48:05 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 8:48:05 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/fsevents): 8:48:05 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 8:48:05 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/gatsby/node_modules/fsevents): 8:48:05 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 8:48:05 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/gatsby-recipes/node_modules/fsevents): 8:48:05 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 8:48:05 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/gatsby-plugin-page-creator/node_modules/fsevents): 8:48:05 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 8:48:05 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/gatsby-page-utils/node_modules/fsevents): 8:48:05 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 8:48:05 AM: added 37 packages from 57 contributors, removed 87 packages, updated 170 packages, moved 1 package and audited 2479 packages in 39.464s 8:48:05 AM: 176 packages are looking for funding 8:48:05 AM:   run npm fundfor details 8:48:05 AM: found 360 vulnerabilities (11 low, 145 moderate, 173 high, 31 critical) 8:48:05 AM:   runnpm audit fixto fix them, ornpm audit for details 8:48:05 AM: npm packages installed 8:48:06 AM: Started restoring cached go cache 8:48:06 AM: Finished restoring cached go cache 8:48:06 AM: Installing Go version 1.12 (requested 1.12) 8:48:10 AM: unset GOOS; 8:48:10 AM: unset GOARCH; 8:48:10 AM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64'; 8:48:10 AM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}"; 8:48:10 AM: go version >&2; 8:48:10 AM: export GIMME_ENV="/opt/buildhome/.gimme/env/go1.12.linux.amd64.env" 8:48:10 AM: go version go1.12 linux/amd64 8:48:10 AM: Detected 1 framework(s) 8:48:10 AM: "gatsby" at version "2.29.1" 8:48:10 AM: Installing missing commands 8:48:10 AM: Verify run directory 8:48:10 AM: Section completed: initializing 8:48:12 AM:  8:48:12 AM:   Netlify Build                                                  8:48:12 AM: ──────────────────────────────────────────────────────────────── 8:48:12 AM:  8:48:12 AM: ❯ Version 8:48:12 AM:   @netlify/build 29.5.4 8:48:12 AM:  8:48:12 AM: ❯ Flags 8:48:12 AM:   baseRelDir: true 8:48:12 AM:   buildId: 63dcbc01be0f8c0009f2f7b6 8:48:12 AM:   deployId: 63dcbc01be0f8c0009f2f7b8 8:48:12 AM:  8:48:12 AM: ❯ Current directory 8:48:12 AM:   /opt/build/repo 8:48:12 AM:  8:48:12 AM: ❯ Config file 8:48:12 AM:   No config file was defined: using default values. 8:48:12 AM:  8:48:12 AM: ❯ Context 8:48:12 AM:   production 8:48:12 AM:  8:48:12 AM: ❯ Installing plugins 8:48:12 AM:    - @netlify/plugin-gatsby@3.5.1 8:48:27 AM:  8:48:27 AM: ❯ Loading plugins 8:48:27 AM:    - @netlify/plugin-gatsby@3.5.1 from undefined 8:48:29 AM:  8:48:29 AM:   Plugin "@netlify/plugin-gatsby" internal error                 8:48:29 AM: ──────────────────────────────────────────────────────────────── 8:48:29 AM:  8:48:29 AM:   Error message 8:48:29 AM:   Could not import plugin: 8:48:29 AM:   Error: Cannot find module '@gatsbyjs/reach-router' 8:48:29 AM:   Require stack: 8:48:29 AM:   - /opt/build/repo/.netlify/plugins/node_modules/@netlify/plugin-gatsby/lib/templates/api/gatsbyFunction.js 8:48:29 AM:   - /opt/build/repo/.netlify/plugins/node_modules/@netlify/plugin-gatsby/lib/templates/handlers.js 8:48:29 AM:   - /opt/build/repo/.netlify/plugins/node_modules/@netlify/plugin-gatsby/lib/helpers/functions.js 8:48:29 AM:   - /opt/build/repo/.netlify/plugins/node_modules/@netlify/plugin-gatsby/lib/index.js 8:48:29 AM:  8:48:29 AM:   Plugin details 8:48:29 AM:   Package:        @netlify/plugin-gatsby 8:48:29 AM:   Version:        3.5.1 8:48:29 AM:   Repository:     git+https://github.com/netlify/netlify-plugin-gatsby.git 8:48:29 AM: Failed during stage 'building site': Build script returned non-zero exit code: 3 (https://ntl.fyi/exit-code-3) 8:48:29 AM:   npm link:       https://www.npmjs.com/package/@netlify/plugin-gatsby 8:48:29 AM:   Report issues:  https://github.com/netlify/netlify-plugin-gatsby/issues 8:48:29 AM:  8:48:29 AM:   Error location 8:48:29 AM:   While loading "@netlify/plugin-gatsby" from undefined 8:48:29 AM:       at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) 8:48:29 AM:       at Function.Module._load (node:internal/modules/cjs/loader:841:27) 8:48:29 AM:       at Module.require (node:internal/modules/cjs/loader:1067:19) 8:48:29 AM:       at require (node:internal/modules/cjs/helpers:103:18) 8:48:29 AM:       at Object.<anonymous> (/opt/build/repo/.netlify/plugins/node_modules/@netlify/plugin-gatsby/lib/templates/api/gatsbyFunction.js:10:24) 8:48:29 AM:       at Module._compile (node:internal/modules/cjs/loader:1165:14) 8:48:29 AM:       at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10) 8:48:29 AM:       at Module.load (node:internal/modules/cjs/loader:1043:32) 8:48:29 AM:       at Function.Module._load (node:internal/modules/cjs/loader:878:12) 8:48:29 AM:       at Module.require (node:internal/modules/cjs/loader:1067:19) 8:48:29 AM:  8:48:29 AM:   Error properties 8:48:29 AM:   { code: 'MODULE_NOT_FOUND' } 8:48:29 AM:  8:48:29 AM:   Resolved config 8:48:29 AM:   build: 8:48:29 AM:     command: gatsby build 8:48:29 AM:     commandOrigin: ui 8:48:29 AM:     publish: /opt/build/repo/public 8:48:29 AM:     publishOrigin: ui 8:48:29 AM:   plugins: 8:48:29 AM:     - inputs: {} 8:48:29 AM:       package: '@netlify/plugin-gatsby' 8:48:29 AM: Caching artifacts 8:48:29 AM: Started saving node modules 8:48:29 AM: Finished saving node modules 8:48:29 AM: Started saving build plugins 8:48:29 AM: Finished saving build plugins 8:48:29 AM: Started saving pip cache 8:48:29 AM: Finished saving pip cache 8:48:29 AM: Started saving emacs cask dependencies 8:48:29 AM: Finished saving emacs cask dependencies 8:48:29 AM: Started saving maven dependencies 8:48:29 AM: Finished saving maven dependencies 8:48:29 AM: Started saving boot dependencies 8:48:29 AM: Finished saving boot dependencies 8:48:29 AM: Started saving rust rustup cache 8:48:29 AM: Finished saving rust rustup cache 8:48:29 AM: Started saving go dependencies 8:48:29 AM: Finished saving go dependencies 8:48:29 AM: Build failed due to a plugin error: Build script returned non-zero exit code: 3 8:48:29 AM: Failing build: Failed to build site 8:48:29 AM: Finished processing build request in 1m14.807s

Solved it by installing @gatsbyjs/reach-router yarn add @gatsbyjs/reach-router

It worked like a charm! Thank you

I had a similar issue. Netlify deployments were broken.
Gatsby version: 2.24.91
Solved it by installing @gatsbyjs/reach-router yarn add @gatsbyjs/reach-router

Thanks work, for people using React 16, you can use this npm (wori with 16,17 React)
https://www.npmjs.com/package/@gatsbyjs/reach-router/v/1.3.9

Thanks for the reports evenryone. The issue seems to be that it's trying to import the Gatsby Functions template, even in old versions of Gatsby that don't support it. That template uses the Gatsby reach-router fork that wasn't included in the old versions.

That did it. Thank you for the super fast fix. 🚀

Thank you all for notifying us on this issue, we've pushed out a fix for the reach-router error here

I have similar problem and i am not programmer, I am using stackbit v1, contentful and after they deprecated v1, my sites stopped updating
2:38:26 PM: Build ready to start
2:38:40 PM: build-image version: 9495be345de05eb8e91837e5d92c5afd0dbd65f6 (focal)
2:38:40 PM: buildbot version: 9495be345de05eb8e91837e5d92c5afd0dbd65f6
2:38:40 PM: Building without cache
2:38:40 PM: Starting to prepare the repo for build
2:38:41 PM: No cached dependencies found. Cloning fresh repo
2:38:41 PM: git clone --filter=blob:none https://github.com/ibnhabib/interesting-neptune
2:38:41 PM: Preparing Git Reference refs/heads/master
2:38:41 PM: Parsing package.json dependencies
2:38:43 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'public' versus '' in the Netlify UI
2:38:43 PM: Different build command detected, going to use the one specified in the Netlify configuration file: './stackbit-build.sh' versus '' in the Netlify UI
2:38:43 PM: Starting build script
2:38:43 PM: Installing dependencies
2:38:43 PM: Python version set to 2.7
2:38:44 PM: Downloading and installing node v12.18.0...
2:38:44 PM: Downloading https://nodejs.org/dist/v12.18.0/node-v12.18.0-linux-x64.tar.xz...
2:40:53 PM: Computing checksum with sha256sum
2:40:53 PM: Checksums matched!
2:40:54 PM: Now using node v12.18.0 (npm v6.14.4)
2:40:54 PM: Started restoring cached build plugins
2:40:54 PM: Finished restoring cached build plugins
2:40:54 PM: Attempting Ruby version 2.7.1, read from environment
2:40:55 PM: Required ruby-2.7.1 is not installed - installing.
2:40:55 PM: Searching for binary rubies, this might take some time.
2:40:55 PM: Found remote file https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/20.04/x86_64/ruby-2.7.1.tar.bz2
2:40:55 PM: Checking requirements for ubuntu.
2:40:55 PM: Requirements installation successful.
2:40:55 PM: ruby-2.7.1 - #configure
2:40:55 PM: ruby-2.7.1 - #download
2:40:55 PM: ruby-2.7.1 - #validate archive
2:40:59 PM: ruby-2.7.1 - #extract
2:41:01 PM: ruby-2.7.1 - #validate binary
2:41:01 PM: ruby-2.7.1 - #setup
2:41:02 PM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1@global
2:41:02 PM: ruby-2.7.1 - #importing gemset /opt/buildhome/.rvm/gemsets/global.gems........................................
2:41:02 PM: ruby-2.7.1 - #generating global wrappers........
2:41:02 PM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1
2:41:02 PM: ruby-2.7.1 - #importing gemsetfile /opt/buildhome/.rvm/gemsets/default.gems evaluated to empty gem list
2:41:02 PM: ruby-2.7.1 - #generating default wrappers........
2:41:02 PM: Using /opt/buildhome/.rvm/gems/ruby-2.7.1
2:41:03 PM: Using Ruby version 2.7.1
2:41:03 PM: Using PHP version 8.0
2:41:03 PM: Started restoring cached corepack dependencies
2:41:03 PM: Finished restoring cached corepack dependencies
2:41:03 PM: No npm workspaces detected
2:41:03 PM: Started restoring cached node modules
2:41:03 PM: Finished restoring cached node modules
2:41:03 PM: Bypassing sha validation. Running pre & post install scripts
2:41:03 PM: Installing npm packages using npm version 6.14.4
2:41:25 PM: > node-sass@4.14.0 install /opt/build/repo/node_modules/node-sass
2:41:25 PM: > node scripts/install.js
2:41:25 PM: Downloading binary from https://github.com/sass/node-sass/releases/download/v4.14.0/linux-x64-72_binding.node
2:41:26 PM: Download complete
2:41:26 PM: Binary saved to /opt/build/repo/node_modules/node-sass/vendor/linux-x64-72/binding.node
2:41:26 PM: Caching binary to /opt/buildhome/.npm/node-sass/4.14.0/linux-x64-72_binding.node
2:41:26 PM: > core-js@2.6.12 postinstall /opt/build/repo/node_modules/core-js
2:41:26 PM: > node -e "try{require('./postinstall')}catch(e){}"
2:41:26 PM: > core-js-pure@3.10.2 postinstall /opt/build/repo/node_modules/core-js-pure
2:41:26 PM: > node -e "try{require('./postinstall')}catch(e){}"
2:41:26 PM: > core-js@3.10.2 postinstall /opt/build/repo/node_modules/gatsby/node_modules/core-js
2:41:26 PM: > node -e "try{require('./postinstall')}catch(e){}"
2:41:27 PM: > gatsby-telemetry@1.10.1 postinstall /opt/build/repo/node_modules/gatsby-telemetry
2:41:27 PM: > node src/postinstall.js || true
2:41:27 PM: > gatsby-cli@2.19.2 postinstall /opt/build/repo/node_modules/gatsby/node_modules/gatsby-cli
2:41:27 PM: > node scripts/postinstall.js
2:41:27 PM: > gatsby@2.25.4 postinstall /opt/build/repo/node_modules/gatsby
2:41:27 PM: > node scripts/postinstall.js
2:41:27 PM: > node-sass@4.14.0 postinstall /opt/build/repo/node_modules/node-sass
2:41:27 PM: > node scripts/build.js
2:41:27 PM: Binary found at /opt/build/repo/node_modules/node-sass/vendor/linux-x64-72/binding.node
2:41:27 PM: Testing binary
2:41:27 PM: Binary is fine
2:41:29 PM: npm WARN azimuth@0.0.1 No repository field.
2:41:29 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
2:41:29 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:41:29 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/watchpack/node_modules/fsevents):
2:41:29 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:41:29 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
2:41:29 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:41:29 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/babel-plugin-add-module-exports/node_modules/fsevents):
2:41:29 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:41:29 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/gatsby/node_modules/fsevents):
2:41:29 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:41:29 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/gatsby-recipes/node_modules/fsevents):
2:41:29 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:41:29 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/gatsby-plugin-page-creator/node_modules/fsevents):
2:41:29 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:41:29 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/gatsby-page-utils/node_modules/fsevents):
2:41:29 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:41:29 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
2:41:29 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:41:29 PM: added 2255 packages from 929 contributors and audited 2269 packages in 25.492s
2:41:30 PM: 200 packages are looking for funding
2:41:30 PM:   run npm fund for details
2:41:30 PM: found 254 vulnerabilities (11 low, 77 moderate, 135 high, 31 critical)
2:41:30 PM:   run npm audit fix to fix them, or npm audit for details
2:41:30 PM: npm packages installed
2:41:30 PM: Started restoring cached go cache
2:41:30 PM: Finished restoring cached go cache
2:41:30 PM: Installing Go version 1.14.4 (requested 1.14.4)
2:41:34 PM: go version go1.14.4 linux/amd64
2:41:34 PM: Detected 1 framework(s)
2:41:34 PM: "gatsby" at version "2.25.4"
2:41:34 PM: Installing missing commands
2:41:34 PM: Verify run directory
2:41:34 PM: Section completed: initializing
2:41:36 PM:
2:41:36 PM:   Netlify Build
2:41:36 PM: ────────────────────────────────────────────────────────────────
2:41:36 PM:
2:41:36 PM: ❯ Version
2:41:36 PM:   @netlify/build 29.5.4
2:41:36 PM:
2:41:36 PM: ❯ Flags
2:41:36 PM:   baseRelDir: true
2:41:36 PM:   buildId: 63e37ba25efcfd16f0e5ca7c
2:41:36 PM:   deployId: 63e37ba25efcfd16f0e5ca7e
2:41:36 PM:
2:41:36 PM: ❯ Current directory
2:41:36 PM:   /opt/build/repo
2:41:36 PM:
2:41:36 PM: ❯ Config file
2:41:36 PM:   /opt/build/repo/netlify.toml
2:41:36 PM:
2:41:36 PM: ❯ Context
2:41:36 PM:   production
2:41:36 PM:
2:41:36 PM: ❯ Installing plugins
2:41:36 PM:    - netlify-plugin-amp-server-side-rendering@1.0.2
2:41:36 PM:    - netlify-plugin-gatsby-cache@0.3.0
2:41:36 PM:    - @netlify/plugin-lighthouse@4.0.7
2:41:36 PM:    - netlify-plugin-image-optim@0.4.0
2:41:36 PM:    - netlify-plugin-hashfiles@4.0.2
2:41:36 PM:    - netlify-plugin-inline-critical-css@2.0.0
2:41:36 PM:    - netlify-plugin-inline-source@1.0.4
2:41:36 PM:    - @netlify/plugin-sitemap@0.8.1
2:41:36 PM:    - netlify-plugin-minify-html@0.3.1
2:41:36 PM:    - @netlify/plugin-gatsby@1.0.3
2:42:27 PM:
2:42:27 PM: ❯ Loading plugins
2:42:27 PM:    - netlify-plugin-amp-server-side-rendering@1.0.2 from Netlify app
2:42:27 PM:    - netlify-plugin-gatsby-cache@0.3.0 from Netlify app
2:42:27 PM:    - @netlify/plugin-lighthouse@4.0.7 from Netlify app
2:42:27 PM:    - netlify-plugin-image-optim@0.4.0 from Netlify app
2:42:27 PM:    - netlify-plugin-hashfiles@4.0.2 from Netlify app
2:42:27 PM:    - netlify-plugin-inline-critical-css@2.0.0 from Netlify app
2:42:27 PM:    - netlify-plugin-inline-source@1.0.4 from Netlify app
2:42:27 PM:    - @netlify/plugin-sitemap@0.8.1 from Netlify app
2:42:27 PM:    - netlify-plugin-minify-html@0.3.1 from Netlify app
2:42:27 PM:    - @netlify/plugin-gatsby@1.0.3 from undefined
2:42:27 PM:
2:42:27 PM: ❯ Outdated plugins
2:42:27 PM:    - @netlify/plugin-gatsby@1.0.3: latest version is 3.5.1
2:42:27 PM:      Migration guide: https://ntl.fyi/gatsby-plugin-migration
2:42:27 PM:      To upgrade this plugin, please remove it from "netlify.toml" and install it from the Netlify plugins directory instead (https://app.netlify.com/plugins)
2:42:34 PM:
2:42:34 PM:   1. netlify-plugin-gatsby-cache (onPreBuild event)
2:42:34 PM: ────────────────────────────────────────────────────────────────
2:42:34 PM:
2:42:34 PM: No Gatsby cache found. Building fresh.
2:42:34 PM:
2:42:34 PM: (netlify-plugin-gatsby-cache onPreBuild completed in 7ms)
2:42:34 PM:
2:42:34 PM:   2. @netlify/plugin-gatsby (onPreBuild event)
2:42:34 PM: ────────────────────────────────────────────────────────────────
2:42:34 PM:
2:42:34 PM: No Gatsby cache found. Building fresh.
2:42:34 PM:
2:42:34 PM:   Plugin "@netlify/plugin-gatsby" failed
2:42:34 PM: ────────────────────────────────────────────────────────────────
2:42:34 PM:
2:42:34 PM:   Error message
2:42:34 PM:   Error: Could not load gatsby-config.js
2:42:34 PM:   Cannot find module './site-metadata.json'
2:42:34 PM:   Require stack:
2:42:34 PM:   - /opt/build/repo/gatsby-config.js
2:42:34 PM:   - /opt/build/repo/.netlify/plugins/node_modules/@netlify/plugin-gatsby/src/index.js
2:42:34 PM:
2:42:34 PM:   Plugin details
2:42:34 PM:   Package:        @netlify/plugin-gatsby
2:42:34 PM:   Version:        1.0.3
2:42:34 PM:   Repository:     git+https://github.com/netlify/netlify-plugin-gatsby.git
2:42:34 PM:   npm link:       https://www.npmjs.com/package/@netlify/plugin-gatsby
2:42:34 PM:   Report issues:  https://github.com/netlify/netlify-plugin-gatsby/issues
2:42:34 PM:
2:42:34 PM:   Error location
2:42:34 PM:   In "onPreBuild" event in "@netlify/plugin-gatsby" from undefined
2:42:34 PM:
2:42:34 PM:   Resolved config
2:42:34 PM:   build:
2:42:34 PM:     command: ./stackbit-build.sh
2:42:34 PM:     commandOrigin: config
2:42:34 PM:     environment:
2:42:34 PM:       - CONTENTFUL_ACCESS_TOKEN
2:42:34 PM:       - CONTENTFUL_DELIVERY_TOKEN
2:42:34 PM:       - CONTENTFUL_SPACE_ID
2:42:34 PM:       - NETLIFY_GRAPH_TOKEN
2:42:34 PM:       - ONEGRAPH_AUTHLIFY_TOKEN
2:42:34 PM:       - STACKBIT_API_KEY
2:42:34 PM:     publish: /opt/build/repo/public
2:42:34 PM:     publishOrigin: config
2:42:34 PM:   plugins:
2:42:34 PM:     - inputs: {}
2:42:34 PM:       origin: ui
2:42:34 PM:       package: netlify-plugin-amp-server-side-rendering
2:42:34 PM:     - inputs: {}
2:42:34 PM:       origin: ui
2:42:36 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
2:42:34 PM:       package: netlify-plugin-gatsby-cache
2:42:34 PM:     - inputs: {}
2:42:34 PM:       origin: ui
2:42:34 PM:       package: '@netlify/plugin-lighthouse'
2:42:34 PM:     - inputs: {}
2:42:34 PM:       origin: ui
2:42:34 PM:       package: netlify-plugin-image-optim
2:42:34 PM:     - inputs: {}
2:42:34 PM:       origin: ui
2:42:34 PM:       package: netlify-plugin-hashfiles
2:42:34 PM:     - inputs: {}
2:42:34 PM:       origin: ui
2:42:34 PM:       package: netlify-plugin-inline-critical-css
2:42:34 PM:     - inputs: {}
2:42:34 PM:       origin: ui
2:42:34 PM:       package: netlify-plugin-inline-source
2:42:34 PM:     - inputs: {}
2:42:34 PM:       origin: ui
2:42:34 PM:       package: '@netlify/plugin-sitemap'
2:42:34 PM:     - inputs: {}
2:42:34 PM:       origin: ui
2:42:34 PM:       package: netlify-plugin-minify-html
2:42:34 PM:     - inputs: {}
2:42:34 PM:       package: '@netlify/plugin-gatsby'
2:42:34 PM: Caching artifacts
2:42:34 PM: Started saving node modules
2:42:34 PM: Finished saving node modules
2:42:34 PM: Started saving build plugins
2:42:34 PM: Finished saving build plugins
2:42:34 PM: Started saving corepack cache
2:42:34 PM: Finished saving corepack cache
2:42:34 PM: Started saving pip cache
2:42:34 PM: Finished saving pip cache
2:42:34 PM: Started saving emacs cask dependencies
2:42:34 PM: Finished saving emacs cask dependencies
2:42:34 PM: Started saving maven dependencies
2:42:34 PM: Finished saving maven dependencies
2:42:34 PM: Started saving boot dependencies
2:42:34 PM: Finished saving boot dependencies
2:42:34 PM: Started saving rust rustup cache
2:42:34 PM: Finished saving rust rustup cache
2:42:34 PM: Started saving go dependencies
2:42:34 PM: Finished saving go dependencies
2:42:36 PM: Cached Ruby version 2.7.1
2:42:36 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
2:42:36 PM: Failing build: Failed to build site
2:42:36 PM: Finished processing build request in 3m55.43s

authors: RadasLove anton-g ascorbic ibnhabib taty2010 tekhaus ummahusla wslyvh

repo: netlify/netlify-plugin-gatsby


text:
test: setup cypress test running for variant of default demo with all flags enabled

Description
This is extracted from https://github.com/netlify/next-runtime/pull/2286 to standalone PR to prepare setup in repo to run cypress default demo tests with all upcoming feature flags enabled (as there will be some assertions that need to be conditional or potentially tests / entire describe blocks skipped). As-is it will just do same thing as current default demo and extracting it to separate PR just limits to diff on my PR + make the setup available for blobs store related work (if needed).
New Netlify site was created ( https://app.netlify.com/sites/netlify-plugin-nextjs-demo-all-flags/overview ) that is build from same directory as current default demo site demo. As new feature flags are added - we should be adding those via Environment Variables to new test site in Netlify UI (netlify.toml is shared so we can't add them there without making default demo also using all the new feature flags)
Documentation

Tests

You can test this change yourself like so:

TODO

Relevant links (GitHub issues, etc.) or a picture of cute animal

Superseded by v5.

source: gharchive/pull-request

authors: pieh serhalp

repo: netlify/next-runtime

license: MIT

license_type: permissive

license_source: github-api


text:
用不了啊

可以进去，但不能使用

请 把网址贴出来， 有google chrome的network抓包更好。

超时关闭.

source: gharchive/issue

repo: netptop/siteproxy


text:
Routes Grouping  with .post HookTrigger methods doesn't take into account group prefix

When grouping methods together with
https://github.com/netreconlab/parse-server-swift/blob/0538fcaac76f508e524554b6a498c4e020fc9c98/Sources/ParseServerSwift/Extensions/ParseHookTrigger%2BVapor.swift#L891-L900
the prefix of the group, ie "user"
    func boot(routes: RoutesBuilder) throws {

        let usersGroup = routes.grouped("user")

        usersGroup.post("login", "after",
                        object: User.self,
                        trigger: .afterLogin,
                        use: afterLogin
        )

    }

which produces a ParseError when called
  Error: {"message":{"status":404,"headers":{"content-length":"35","content-type":"application/json; charset=utf-8","connection":"keep-alive","date":"Wed, 10 Jan 2024 02:20:30 GMT"},"buffer":{"type":"Buffer","data":[123,34,114,101,97,115,111,110,34,58,34,78,111,116,32,70,111,117,110,100,34,44,34,101,114,114,111,114,34,58,116,114,117,101,125]},"text":"{\"reason\":\"Not Found\",\"error\":true}","data":{"reason":"Not Found","error":true}},"code":141} {"className":"_User","error":{"code":141,"message":{"buffer":{"data":[123,34,114,101,97,115,111,110,34,58,34,78,111,116,32,70,111,117,110,100,34,44,34,101,114,114,111,114,34,58,116,114,117,101,125],"type":"Buffer"},"data":{"error":true,"reason":"Not Found"},"headers":{"connection":"keep-alive","content-length":"35","content-type":"application/json; charset=utf-8","date":"Wed, 10 Jan 2024 02:20:30 GMT"},"status":404,"text":"{\"reason\":\"Not Found\",\"error\":true}"}},"triggerType":"afterLogin","user":"WnjQEA6FsE"}
/Users/jayson/Projects/heroku/node_modules/parse-server/lib/ParseServer.js:261
          throw err;
          ^

ParseError: [object Object]
    at resolveError (/Users/jayson/Projects/heroku/node_modules/parse-server/lib/triggers.js:657:17)
    at error (/Users/jayson/Projects/heroku/node_modules/parse-server/lib/triggers.js:431:17)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 141
}

the afterLogin method is the same from the routes.swift but modified to work with Collections
func afterLogin(req: Request) async throws -> ParseHookResponse<Bool> {

        // Note that `ParseHookResponse<Bool>` means a "successful"
        // response will return a "Bool" type. Bool is the standard response with
        // a "true" response meaning everything is okay or continue.
        if let error: ParseHookResponse<Bool> = checkHeaders(req) {
            return error
        }
        let parseRequest = try req.content
            .decode(ParseHookTriggerObjectRequest<User, User>.self)

        req.logger.info("A user has logged in: \(parseRequest)")

        return ParseHookResponse(success: true)
    }

I tried pinpointing where it all goes wrong in ParseHookTrigger%2BVapor.swift but couldn't.
to make it work, I had to make the code as such:

    func boot(routes: RoutesBuilder) throws {

        //let usersGroup = routes.grouped("user")

        routes.post("user", "login", "after",
                        object: User.self,
                        trigger: .afterLogin,
                        use: afterLogin
        )

    }

thanks,

Can you explain how this differs from https://github.com/netreconlab/parse-server-swift/discussions/38#discussioncomment-6255285 and not fixed in #41?

This only happened now when I first tried using a HookTrigger.
The last time they I was using it for HookFunctions and was fixed by your update.
so it has something to do with the methods that use the .post(_ path: PathComponent..., object: trigger: use:) I believe.

Hmm. reminding me of #41 led me to check the changes you made on ParseHookFunction.swift and I think copying that change to ParseHookTrigger.swift fixed the issue.
I'll do a pull request.

Solved in #55

repo: netreconlab/parse-server-swift


text:
message is not serializable for bin format - enricher with kcg pipeline

Describe the bug
I am getting below error while using kcg pipline with enricher. I am not getting any data in clickhouse.
To Reproduce
Using this entrypoint
ENTRYPOINT [ "/bin/bash", "-c", "./goflow2 -transport.file.sep= -format=bin | ./enricher -transport.kafka.brokers=kafka:9092 -transport=kafka -transport.kafka.topic=flows -format=bin -db.asn=GeoLite2-ASN.mmdb -db.country=GeoLite2-Country.mmdb"]
Captures
-format=bin:
kcg-goflow2-1  | time="2023-08-30T14:07:49Z" level=error msg="message is not serializable for bin format"
kcg-goflow2-1  | time="2023-08-30T14:07:49Z" level=error msg="message is not serializable for bin format"
kcg-goflow2-1  | time="2023-08-30T14:07:49Z" level=error msg="message is not serializable for bin format"
kcg-goflow2-1  | time="2023-08-30T14:07:49Z" level=error msg="message is not serializable for bin format"
kcg-goflow2-1  | time="2023-08-30T14:07:49Z" level=error msg="message is not serializable for bin format"
kcg-goflow2-1  | time="2023-08-30T14:07:49Z" level=error msg="message is not serializable for bin format"
kcg-goflow2-1  | time="2023-08-30T14:07:49Z" level=error msg="message is not serializable for bin format"
kcg-goflow2-1  | time="2023-08-30T14:07:49Z" level=error msg="message is not serializable for bin format"
JSON:
-format default:
kcg-goflow2-1  | {"type":2,"sequence_num":175547948,"sampling_rate":1024,"sampler_address":"ZgKJRg==","bytes":1460,"packets":1,"src_addr":"kktySQ==","dst_addr":"3x45Tw==","etype":2048,"proto":6,"src_port":443,"dst_port":29704,"in_if":13,"out_if":27,"tcp_flags":16,"next_hop":"rBG8Bg=="}
kcg-goflow2-1  | {"type":2,"sequence_num":175547948,"sampling_rate":1024,"sampler_address":"ZgKJRg==","bytes":1480,"packets":1,"src_addr":"E1CNRw==","dst_addr":"Z55wg==","etype":2048,"proto":6,"src_port":443,"dst_port":63165,"in_if":13,"out_if":25,"tcp_flags":24,"next_hop":"rB/2Ag=="}
kcg-goflow2-1  | {"type":2,"sequence_num":175547948,"sampling_rate":1024,"sampler_address":"ZgKJRg==","bytes":1348,"packets":1,"src_addr":"Rx1B+A==","dst_addr":"b1i63w==","etype":2048,"proto":17,"src_port":443,"dst_port":49588,"in_if":13,"out_if":38,"ip_tos":112,"dst_as":11455,"next_hop":"rApl5g=="}
GoFlow2:

Version: [e.g. v2.0.0]
Environment: [e.g. Kubernetes, Docker, Debian package]
OS: [e.g. Linux Ubuntu Server 23.04]

Hi @fyzali,
Thank you for the report, good catch.
I need to confirm this but I think it's mostly due to the lack of MarshalBinary function for the enricher protobuf.
The JSON is also the default protobuf one and lacks quite a few things.
For GoFlow2, it's present here:
https://github.com/netsampler/goflow2/blob/026fef546e9f116630e7abc658c859295f83cc19/producer/proto/messages.go#L31-L35
The enricher isn't as updated as the main decoder but this should be fixable in a short time.
I would need to wrap the new fields and initial protobuf into a new structure.

Feel free to re-open if needed

Getting same error on Netflow v5 and v9
kcg-goflow2-1  | time="2023-09-01T14:40:44Z" level=warning msg="template error" count=1 error="receiver: message from [::ffff:123.112.137.70]:25893 NetFlowV9 [version:9 type:Decode obsDomainId:273: templateId:259] Error template not found" hostname= port=2055 scheme=netflow
kcg-goflow2-1  | time="2023-09-01T14:40:45Z" level=warning msg="template error" count=1 error="receiver: message from [::ffff:123.112.137.70]:25893 NetFlowV9 [version:9 type:Decode obsDomainId:273: templateId:259] Error template not found" hostname= port=2055 scheme=netflow
kcg-goflow2-1  | time="2023-09-01T14:40:45Z" level=warning msg="template error" count=1 error="receiver: message from [::ffff:123.112.137.70]:25893 NetFlowV9 [version:9 type:Decode obsDomainId:273: templateId:259] Error template not found" hostname= port=2055 scheme=netflow
kcg-goflow2-1  | time="2023-09-01T14:40:45Z" level=warning msg="template error" count=1 error="receiver: message from [::ffff:123.112.137.70]:25893 NetFlowV9 [version:9 type:Decode obsDomainId:273: templateId:259] Error template not found" hostname= port=2055 scheme=netflow

authors: fyzali lspgn


text:
Add profile to build on JDK 14

Motivation:
JDK 14 was released and need some special settings to be able to build with. Also there seems to be one regression that we need to workaround for now.
Modifications:

Add maven profile for JDK 14
Update blockhound version to be able to work on JDK 14
Add workaround for possible JDK 14 regression

Result:
Be able to build on JDK 14

@netty-bot test this please

@netty-bot test this please

repo: netty/netty


text:
Revert test debugging flags and update surefire/failsafe

Motivation:
The functionality provided by #11011 already exists natively in the surefire/failsafe plugins by setting the -Dmaven.surefire.debug flag.
Modification:
Remove redundant Maven profile.
Also upgrade the surefire/failsafe versions, so they cope better when tests prints to STDOUT.
Result:
Less stuff in our pom.xml file, and better console output when our tests are printing stuff.

doh! ... Good catch!

authors: chrisvest normanmaurer


text:
Delay possibility to reuse transaction id when query is failing becau…

…se of timeout
Motivation:
We should try to make it as unlikely as possible that we will reuse a transaction for a query while the remote peer still might send the response for the previously timed out query. Failing to do so put us in risk that we will not be able to map the response correctly.
This reduces the risk of the following scenario:

Query is send to the remote nameeserver
Query is failed as the remote nameserver did not respond in the configured time
New query is send which uses the same transaction id as the failed one. While we use a random to generate these this can still happen as we only have 16bits for the id
nameserver sends back the response for the first query (that we already failed as timed out)
We lookup the query for the id and find the new one and try to complete it with the response for the "old query".
This fails as validation of hostname etc not matches.

Modifications:
If we fail a query because of a timeout delay the removal of the id from the context map. This will make the id not-reusable until the removal actually take place.
Result:
Much less likely to reuse an id while the remote nameserver might still respond to the old query

Thanks to everyone for the review.


text:
ByteString introduced as AsciiString super class

Motivation:
The usage and code within AsciiString has exceeded the original design scope for this class. Its usage as a binary string is confusing and on the verge of violating interface assumptions in some spots.
Modifications:

ByteString will be created as a base class to AsciiString. All of the generic byte handling processing will live in ByteString and all the special character encoding will live in AsciiString.

Results:
The AsciiString interface will be clarified. Users of AsciiString can now be clear of the limitations the class imposes while users of the ByteString class don't have to live with those limitations.

@trustin @nmittler @buchgr - FYI.

@netkins build

@Scottmitch looks great overall! Just a few questions/comments.

@nmittler - Thanks for review! I think I got all your comments...feel free to take a look.

Thanks @Scottmitch! Will review today.

@trustin - Sounds good.  Ping me when you are finished.

@Scottmitch Review finished. Perhaps we don't need AsciiString anymore and we should move textual operations to a utility method? See here.

Moving ByteString, AsciiString and ByteVisitor to netty-common (since it's not limited to writing a codec anymore)
@trustin - We may be creating a circular dependency here. ByteString exposes methods that take ByteBuf types...and so we would have to add netty-buffer as a dependency of netty-common but the netty-buffer package already depends upon netty-common. We may have to introduce an abstraction layer...or move some other stuff....any suggestions?

Those methods are just shortcut methods. We could move them to ByteBufUtil?

Review done. Please ping me for another round. Thank you for your patience!

Moving ByteString, AsciiString and ByteVisitor to netty-common (since it's not limited to writing a codec anymore)

@trustin - We may be creating a circular dependency here. ByteString exposes methods that take ByteBuf types...and so we would have to add netty-buffer as a dependency of netty-common but the netty-buffer package already depends upon netty-common. We may have to introduce an abstraction layer...or move some other stuff....any suggestions?

Those methods are just shortcut methods. We could move them to ByteBufUtil?

Good idea. I had to manually do some conversions which I was leaning on ByteBuf to do for me.  Please review.  I'm wondering if I should worry about manually releasing the ByteBuffer object I allocate to do the conversion...

@trustin - Ready for another round.

@Scottmitch Looks great! Please cherry-pick once you make the getBytes() methods private. If you are inclined to making them public, we could move it somewhere more appropriate.

@trustin - Methods made private for now.  As you said we can always increase visibility later.  I'll pull this in after https://github.com/netty/netty/pull/3626#discussion_r28297248.

@buchgr - FYI.  I'm going to pull this in after your #3626 PR.  This may cause a bit of heart-ache for your headers optimization work, but hopefully not much if you are focused mostly on DefaultHeaders.

@Scottmitch thanks! Will update once I get to work!

PR https://github.com/netty/netty/pull/3631 will serve to review the forward-port into master.

Cherry-picked into 4.1 (9a7a85d and e36c143)

authors: Scottmitch buchgr nmittler trustin


text:
Reduce ByteBuffer duplication when resizing pooled direct ByteBufs

Motivation
Currently when use of Unsafe is disabled and an internal reallocation is performed for a direct PooledByteBuf, a one-off temporary duplicate is made of both the source and destination backing nio buffers so that the copy can be done in a threadsafe manner.
The need for this can be reduced by sharing the temporary duplicate buffers that are already stored in the corresponding PooledByteBuf instances.
Modifications
Change PoolArena#memoryCopy(...) args so that it takes a temp source nio buffer (which may be null) in addition to the source memory ref, and takes the new destination PooledByteBuf instance instead of the destination mem ref and offset.
Use these existing temp buffers if present in the DirectArena impl, and if not share the duplicates back with the other pooling logic - this is done implicitly for the destination buf via use of PooledByteBuf#internalNioBuffer(), and for the source buf by returning it from the method (instead of void).
Result
Fewer temporary allocations when resizing direct pooled ByteBufs in the non-Unsafe case

@netty-bot test this please

@njhill honestly I wonder if this change really worth it... I mean it makes things more complex and resizing should be "hopefully" not happen too often. Or I am missing anything ?

@normanmaurer that's a fair point... I noticed this while looking closer at the underlying buffer manipulation done in ByteToMessageDecoder cumulation but you are probably right re the relative frequency not being big high to matter. Let me remove the "more complex" half of the change ... the other part is a slight simplification if anything imho

@netty-bot test this please

@njhill can you update the commit message and pr description to match what you did now ?

@normanmaurer done

@netty-bot test this please

@njhill thanks.. and sorry for the delay.

authors: njhill normanmaurer


text:
junipervpn (Pulse Secure) parser

Secure Pulse recently made a change to their syslog format. This has caused the current RSA-provided junipervpn parser (Version 104, updated 2017-12-14 11:40 AM) to stop parsing messages correctly.
SEE: Vendor Knowledge Article: “KB40143 - Syslog format changes in 8.0, 8.1, 8.2 and 8.3”
http://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB40143/
“The string, "Juniper" was removed from the syslog message header and timestamp was added in the correct format in the syslog header.“

This request is being looked into under ticket SMC-14020.
Thanks for sharing this update with us.

authors: jnjkcole manish-rsa

repo: netwitness/nw-logparsers

license_source: bigquery


text:
Dependency in /body module seems to be in the wrong scope.

Problem Description
Dependency "com.networknt:status" in the "body" module is set to the default scope compile. However, it seems that it's only used in the tests with classes [com.networknt.exception.ClientException, com.networknt.status.Status].
        <dependency>
            <groupId>com.networknt</groupId>
            <artifactId>status</artifactId>
        </dependency>

Possible Outcome
This brings redundant compile time dependency not only for light-4j, but also for projects using light-4j. Changing its scope to test can reduce the size of dependency tree.
Solution
To fix the problem, i change the dependency scope to test, recompile the module and run the tests. The module is successfully compiled and all tests have passed after the changes.

@stevehu Could you help me review this issue? Thx :p

@HappyHacker123 You are right. I have merged the PR. Thanks a lot for your help.


text:
Use NSM-envs from the client application

Description
We have a many NSM envs that allow us to configure the NSC in the best possible way:
https://github.com/networkservicemesh/cmd-nsc/blob/main/internal/config/config.go#L31-L43
	Name             string        `default:"nsc" desc:"Name of Network Service Client"`
	ConnectTo        url.URL       `default:"unix:///var/lib/networkservicemesh/nsm.io.sock" desc:"url to connect to NSM" split_words:"true"`
	DialTimeout      time.Duration `default:"5s" desc:"timeout to dial NSMgr" split_words:"true"`
	RequestTimeout   time.Duration `default:"15s" desc:"timeout to request NSE" split_words:"true"`
	MaxTokenLifetime time.Duration `default:"10m" desc:"maximum lifetime of tokens" split_words:"true"`

	Labels    []string `default:"" desc:"A list of client labels with format key1=val1,key2=val2, will be used a primary list for network services" split_words:"true"`
	Mechanism string   `default:"kernel" desc:"Default Mechanism to use, supported values: kernel, vfio" split_words:"true"`

	NetworkServices       []url.URL               `default:"" desc:"A list of Network Service Requests" split_words:"true"`
	AwarenessGroups       awarenessgroups.Decoder `defailt:"" desc:"Awareness groups for mutually aware NSEs" split_words:"true"`
	LogLevel              string                  `default:"INFO" desc:"Log level" split_words:"true"`
	OpenTelemetryEndpoint string                  `default:"otel-collector.observability.svc.cluster.local:4317" desc:"OpenTelemetry Collector Endpoint"`

And we definitely can do it when we use a bare NSC, without any actual client application.
But this is not the main use case for NSM - users can add networkservicemesh annotations:
...
annotations:
    networkservicemesh.io: "kernel://my-networkservice-1/nsm-1"
...

NetworkServices or Mechanism - we can take it from the annotation. But what about others? What if the user wants to add  AwarenessGroups and so on?
Possible solutions:

Use NSM_ prefixed envs that are passed by user and inject them into NSM-containers
Expand the current networkservicemesh.io annotation and add new parameters

@denis-tingaikin @edwarnicke
Any thoughts?

@glazychev-art Could you provide concrete examples of things we might do with them?

@edwarnicke Imagine the case when external client wants set  Mutually Aware Group

@LionelJouin Do you anticipate using the annotations for cases where you need to set a Mutually Aware Group?

@glazychev-art @denis-tingaikin Do we have someone using Webhooks for more complex cases?  Do we have a need ourselves there... or are we trying to get ahead of needs?

@edwarnicke This could be useful for invariant testing. Moreover, I think this is actual question. What if external clients wants to tune up nsc configuration?

@edwarnicke
I think we might be inrested in support next syntax:
networkservicemesh.io: | {{. mechanism }}://{{ .serviceName}}/{{ .interfaceName }}?{{. labels }}
{{.envConfig}

Example:
networkservicemesh.io: | kernel://ns-1/nsm-1
NSM_DIAL_TIMEOUT=5s
NSM_MAX_TOKEN_LIFE_TIME=30s
...

Thoughts?

What if we have multiple Network Services to which a Pod wishes to connect?

What if we have multiple Network Services to which a Pod wishes to connect?

Thats an intresting question.
For this case we need change syntax to this
networkservicemesh.io: |
  {{.envConfig}
  {{. mechanism1 }}://{{ .serviceName1}}/{{ .interfaceName1 }}?{{. labels1}}
  {{. mechanism2 }}://{{ .serviceName2}}/{{ .interfaceName2 }}?{{. labels2}}
  ...
  {{. mechanismN }}://{{ .serviceNameN}}/{{ .interfaceNameN }}?{{. labelsN}}

Or we could simply add a new annotation
networkservicemesh.io/config: |
   {{.envConfig}

I am concerned here are that all the use cases we have so far involve us wanting to tweak our test cases.   Introducing complex parameter tweaking into our test cases makes it less likely that things just 'work' out of the box with a simple single line annotation.

We don't want to use this for testing.
We need this for users who want to enable Mutually Aware Group, or disable heal, or tune something for the specific cluster,.
@edwarnicke Makes sense?

@denis-tingaikin Do we have users currently?

At this moment we dont get any requests.
I also saw that, for local datapath debug  could be super useful to disable data path to avoid ton of icmp requests in traces.


text:
Add task mapping

Fixes: https://github.com/neulab/explainaboard_web/issues/171

This is no longer necessary after the refactoring of DataLab. Thanks @pfliu-nlp !


text:
[BugFix] Model State Reload with Quantized Stubs in SparseAutoModelForCausalLM

Description
Identified a bug in the main branch where the model state fails to reload when using quantized stubs with SparseAutoModelForCausalLM.from_pretrained(...). The issue was due to the reload_model_state method expecting weight files in a local directory, not accounting for remotely hosted model directories.
Solution
Propose downloading the model directory before invoking reload_model_state to ensure weight files are available locally for model state reload.
Testing
Tested with the following script, confirming the fix resolves the issue:
from sparseml.transformers import SparseAutoModelForCausalLM

model_path = "mgoin/llama2.c-stories15M-quant-pt"
m1 = SparseAutoModelForCausalLM.from_pretrained(model_path)

Observations
Before the Fix:
Model state fails to reload due to missing local weight files, as shown in warnings and errors in the logs.
..
..
2024-04-05 17:33:33 sparseml.core.recipe.recipe INFO     Loading recipe from file /home/rahul/.cache/huggingface/hub/models--mgoin--llama2.c-stories15M-quant-pt/snapshots/aa70fc9dc46615b68f935fb5405ae7875b88b716/recipe.yaml
manager stage: Model structure initialized
2024-04-05 17:33:34 sparseml.pytorch.model_load.helpers INFO     Applied an unstaged recipe to the model at mgoin/llama2.c-stories15M-quant-pt
2024-04-05 17:33:34 sparseml.pytorch.model_load.helpers WARNING  Model state was not reloaded for SparseML: could not find model weights for mgoin/llama2.c-stories15M-quant-pt

After the Fix:
2024-04-05 18:31:00 sparseml.pytorch.model_load.helpers INFO     Reloaded model state after SparseML recipe structure modifications from /home/rahul/.cache/huggingface/hub/models--mgoin--llama2.c-stories15M-quant-pt/snapshots/aa70fc9dc46615b68f935fb5405ae7875b88b716

Successfully reloaded model state with the fix.

The snapshot_download can pull down a lot of extra files since it downloads the whole folder. This might interact weirdly with the resolve_recipe call with specifically tries to download the recipe. This works, but I would like to be a bit more selective with the download

Addressed in latest commit @mgoin

Thanks a lot! It's additional complexity but I think good to have

It was a great callout. Really appreciate it.

repo: neuralmagic/sparseml


text:
Tensorboard delayed output

Because of the following issue:
https://github.com/tensorflow/tensorboard/issues/867
tensorboard does not immediately flush outputs on GCS.
It is fixes pretty easily by adding -e GCS_READ_CACHE_MAX_SIZE_MB=0
I may contribute it myself later

not relevant repo, should be in base-image
the issue was resolved in TensorBoard 1.9, we now have 2.5, closing this issue since the problem is outdated

authors: Rauf-Kurbanov YevheniiSemendiak

repo: neuro-inc/cookiecutter-neuro-project


text:
create mutation to change 'missing' status of a column's value

This mutation, changeMissingStatus, should add/remove a value from a column's list of missing values in the store.
As per our Miro refactor draft, a missingValues list will be stored in the column objects in dataDictionary.annotated.
NOTE: Currently, this is referenced in annot-missing-values in the more specific form called declareNotMissing and in annot-categorical as designateAsMissing. The latter, however, is itself missing from the current implementation of annot-continuous-values.

[x] depending components have been checked and are calling this mutation correctly
[x] have unit tests to check functionality
[x] needed store state variables exist already or have been created if not

This would be a good candidate for the proposed, new columns store field.

Currently this is referenced in annot-missing-values in the more specific forms called declareNotMissing' and in annot-categoricalas 'designateAsMissing'. 'designateAsMissing', however, is itself missing from the current implementation ofannot-continuous-values`.

@surchs Does a 'Mark as missing' button make sense for the continuous values component?

Yes, I just noticed it was missing but its component test defines an unused designateAsMissing mutation (now changed to changeMissingStatus). Not planning on implementing it presently.

Closed by #359


text:
Overlay RESTful call remove server 1 and 2 and introduce default channels

@randalburns would it make sense to remove server 1 and 2 from overlay restful call and introduce default channels?
http://mri.ocp.me/open-connectome/api/overlay_api.html
@kunallillaney thinks so because of the integrated backend.

I think this done now.

authors: kunallillaney willgray

repo: neurodata/open-connectome


text:
sct_register_multimodal: algo rigid doesn't work on certain OS

Same command, same data (/Volumes/slevy-4/data/criugm/d_sp_pain_pilot7/mtv_scan)
OS X 10.8.2 (pass)

pass:/Volumes/slevy-4/data/criugm/d_sp_pain_pilot7/mtv_scan $ sct_register_multimodal -i spgr20crop.nii.gz -d spgr10crop.nii.gz -o spgr20to10.nii.gz -p step=1,type=im,algo=slicereg,metric=MeanSquares,gradStep=0.6,iter=15:step=2,type=im,algo=rigid,metric=MeanSquares
Check file existence...
OK: spgr20crop.nii.gz
Check file existence...
OK: spgr10crop.nii.gz
Input parameters:
Source .............. spgr20crop.nii.gz
Destination ......... spgr10crop.nii.gz
Mask ................
Output name ......... spgr20to10.nii.gz
Remove temp files ... 1
Verbose ............. 1
Check if input data are 3D...
Check if destination data is RPI...
Create temporary folder...
mkdir tmp.150525164122
Copy files...
isct_c3d spgr20crop.nii.gz -o tmp.150525164122/src.nii
isct_c3d spgr10crop.nii.gz -o tmp.150525164122/dest.nii
Estimate transformation for step #0...
isct_antsRegistration --dimensionality 3 --transform syn[0.5,3,0] --metric MI[dest.nii,src.nii,1,32] --convergence 0 --shrink-factors 1 --smoothing-sigmas 0mm --restrict-deformation 1x1x0 --output [step0,src.nii_regStep0.nii] --interpolation BSpline[3]
Estimate transformation for step #1...
sct_apply_transfo -i src.nii -d dest.nii -w warp_forward_0.nii.gz -o src_reg.nii -x linear
export FSLOUTPUTTYPE=NIFTI; fslmaths src_reg.nii -thr 0.1 src_reg_th.nii
export FSLOUTPUTTYPE=NIFTI; fslmaths dest.nii -thr 0.1 dest_th.nii
sct_crop_image -i src_reg_th.nii -dim 2 -bmax -o tmp.nii
sct_crop_image -i dest_th.nii -dim 2 -bmax -o tmp.nii
sct_crop_image -i src_reg.nii -o src_reg_crop.nii -dim 2 -start 0 -end 13
sct_crop_image -i dest.nii -o dest_crop.nii -dim 2 -start 0 -end 13
isct_antsSliceRegularizedRegistration -t Translation[0.5] -m MeanSquares[dest_crop.nii,src_reg_crop.nii,1,4,Regular,0.2] -p 3 -i 15 -f 1 -s 0 -v 1 -o [step1,src_reg_crop.nii_regStep1.nii]
Estimate transformation for step #2...
sct_apply_transfo -i src.nii -d dest.nii -w warp_forward_0.nii.gz,warp_forward_1.nii.gz -o src_reg.nii -x linear
isct_c3d dest.nii -pad 0x0x5vox 0x0x5vox 0 -o dest_pad.nii
isct_antsRegistration --dimensionality 3 --transform rigid[0.5] --metric MeanSquares[dest_pad.nii,src_reg.nii,1,4] --convergence 10 --shrink-factors 1 --smoothing-sigmas 0mm --restrict-deformation 1x1x0 --output [step2,src_reg.nii_regStep2.nii] --interpolation BSpline[3]
All_Command_lines_OK
Using double precision for computations.
number of levels = 1
fixed image: dest_pad.nii
moving image: src_reg.nii
Dimension = 3
Number of stages = 1
Use Histogram Matching false
Winsorize image intensities false
Lower quantile = 0
Upper quantile = 1
Stage 1 State
Image metric = MeanSquares
Fixed image = Image (0x7fcbc901bd90)
RTTI typeinfo:   itk::Image<double, 3u>
Reference Count: 2
Modified Time: 604
Debug: Off
Object Name:
Observers:
none
Source: (none)
Source output name: (none)
Release Data: Off
Data Released: False
Global Release Data: Off
PipelineMTime: 0
UpdateMTime: 426
RealTimeStamp: 0 seconds
LargestPossibleRegion:
Dimension: 3
Index: [0, 0, 0]
Size: [39, 40, 24]
BufferedRegion:
Dimension: 3
Index: [0, 0, 0]
Size: [39, 40, 24]
RequestedRegion:
Dimension: 3
Index: [0, 0, 0]
Size: [39, 40, 24]
Spacing: [0.911458, 0.911458, 5]
Origin: [-26.5733, 30.5851, -32.5206]
Direction:
0.993718 5.88326e-08 0.111916
0.0277402 -0.968794 -0.246309
-0.108423 -0.247866 0.962708
IndexToPointMatrix:
0.905732 5.36235e-08 0.559579
0.025284 -0.883016 -1.23155
-0.0988234 -0.22592 4.81354
PointToIndexMatrix:
1.09025 0.030435 -0.118956
6.41287e-08 -1.06291 -0.271945
0.0223832 -0.0492618 0.192542
Inverse Direction:
0.993718 0.0277402 -0.108423
5.84507e-08 -0.968794 -0.247866
0.111916 -0.246309 0.962708
PixelContainer:
ImportImageContainer (0x7fcbc901bc80)
RTTI typeinfo:   itk::ImportImageContainer<unsigned long, double>
Reference Count: 1
Modified Time: 423
Debug: Off
Object Name:
Observers:
none
Pointer: 0x10c130000
Container manages memory: true
Size: 37440
Capacity: 37440
Moving image = Image (0x7fcbc901c1a0)
RTTI typeinfo:   itk::Image<double, 3u>
Reference Count: 2
Modified Time: 605
Debug: Off
Object Name:
Observers:
none
Source: (none)
Source output name: (none)
Release Data: Off
Data Released: False
Global Release Data: Off
PipelineMTime: 0
UpdateMTime: 602
RealTimeStamp: 0 seconds
LargestPossibleRegion:
Dimension: 3
Index: [0, 0, 0]
Size: [39, 40, 14]
BufferedRegion:
Dimension: 3
Index: [0, 0, 0]
Size: [39, 40, 14]
RequestedRegion:
Dimension: 3
Index: [0, 0, 0]
Size: [39, 40, 14]
Spacing: [0.911458, 0.911458, 5]
Origin: [-23.7754, 24.4274, -8.45287]
Direction:
0.993718 5.88326e-08 0.111916
0.0277402 -0.968794 -0.246309
-0.108423 -0.247866 0.962708
IndexToPointMatrix:
0.905732 5.36235e-08 0.559579
0.025284 -0.883016 -1.23155
-0.0988234 -0.22592 4.81354
PointToIndexMatrix:
1.09025 0.030435 -0.118956
6.41287e-08 -1.06291 -0.271945
0.0223832 -0.0492618 0.192542
Inverse Direction:
0.993718 0.0277402 -0.108423
5.84507e-08 -0.968794 -0.247866
0.111916 -0.246309 0.962708
PixelContainer:
ImportImageContainer (0x7fcbc901c080)
RTTI typeinfo:   itk::ImportImageContainer<unsigned long, double>
Reference Count: 1
Modified Time: 599
Debug: Off
Object Name:
Observers:
none
Pointer: 0x10c1c5000
Container manages memory: true
Size: 21840
Capacity: 21840
Weighting = 1
Sampling strategy = none
Number of bins = 32
Radius = 4
Sampling percentage  = 1
Transform = Rigid
Gradient step = 0.5
Update field sigma (voxel space) = 0
Total field sigma (voxel space) = 0
Update field time sigma = 0
Total field time sigma  = 0
Number of time indices = 0
Number of time point samples = 0
Registration using 1 total stages.
Stage 0
iterations = 10
convergence threshold = 1e-06
convergence window size = 10
number of levels = 1
Shrink factors (level 1 out of 1): [1, 1, 1]
smoothing sigmas per level: [0]
using the MeanSquares metric (weight = 1)
Using default NONE metricSamplingStrategy
*** Running rigid registration ***
dyld: lazy symbol binding failed: Symbol not found: ___sincos_stret
Referenced from: /Users/slevy_local/spinalcordtoolbox/bin/osx/isct_antsRegistration
Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: ___sincos_stret
Referenced from: /Users/slevy_local/spinalcordtoolbox/bin/osx/isct_antsRegistration
Expected in: /usr/lib/libSystem.B.dylib

OS X 10.9.5 (tatum)

tatum:~/mtv_scan $ sct_register_multimodal -i spgr20crop.nii.gz -d spgr10crop.nii.gz -o spgr20to10.nii.gz -p step=1,type=im,algo=slicereg,metric=MeanSquares,gradStep=0.6,iter=15:step=2,type=im,algo=rigid,metric=MeanSquares
Check file existence...
OK: spgr20crop.nii.gz
Check file existence...
OK: spgr10crop.nii.gz
Input parameters:
Source .............. spgr20crop.nii.gz
Destination ......... spgr10crop.nii.gz
Mask ................
Output name ......... spgr20to10.nii.gz
Remove temp files ... 1
Verbose ............. 1
Check if input data are 3D...
Check if destination data is RPI...
Create temporary folder...
mkdir tmp.150525164824
Copy files...
isct_c3d spgr20crop.nii.gz -o tmp.150525164824/src.nii
isct_c3d spgr10crop.nii.gz -o tmp.150525164824/dest.nii
Estimate transformation for step #0...
isct_antsRegistration --dimensionality 3 --transform syn[0.5,3,0] --metric MI[dest.nii,src.nii,1,32] --convergence 0 --shrink-factors 1 --smoothing-sigmas 0mm --restrict-deformation 1x1x0 --output [step0,src.nii_regStep0.nii] --interpolation BSpline[3]
Estimate transformation for step #1...
sct_apply_transfo -i src.nii -d dest.nii -w warp_forward_0.nii.gz -o src_reg.nii -x linear
export FSLOUTPUTTYPE=NIFTI; fslmaths src_reg.nii -thr 0.1 src_reg_th.nii
export FSLOUTPUTTYPE=NIFTI; fslmaths dest.nii -thr 0.1 dest_th.nii
sct_crop_image -i src_reg_th.nii -dim 2 -bmax -o tmp.nii
sct_crop_image -i dest_th.nii -dim 2 -bmax -o tmp.nii
sct_crop_image -i src_reg.nii -o src_reg_crop.nii -dim 2 -start 0 -end 13
sct_crop_image -i dest.nii -o dest_crop.nii -dim 2 -start 0 -end 13
isct_antsSliceRegularizedRegistration -t Translation[0.5] -m MeanSquares[dest_crop.nii,src_reg_crop.nii,1,4,Regular,0.2] -p 3 -i 15 -f 1 -s 0 -v 1 -o [step1,src_reg_crop.nii_regStep1.nii]
Estimate transformation for step #2...
sct_apply_transfo -i src.nii -d dest.nii -w warp_forward_0.nii.gz,warp_forward_1.nii.gz -o src_reg.nii -x linear
isct_c3d dest.nii -pad 0x0x5vox 0x0x5vox 0 -o dest_pad.nii
isct_antsRegistration --dimensionality 3 --transform rigid[0.5] --metric MeanSquares[dest_pad.nii,src_reg.nii,1,4] --convergence 10 --shrink-factors 1 --smoothing-sigmas 0mm --restrict-deformation 1x1x0 --output [step2,src_reg.nii_regStep2.nii] --interpolation BSpline[3]
Concatenate transformations...
sct_concat_transfo -w warp_forward_0.nii.gz,warp_forward_1.nii.gz,warp_forward_2.mat -d dest.nii -o warp_src2dest.nii.gz
sct_concat_transfo -w -warp_forward_2.mat,warp_inverse_1.nii.gz,warp_inverse_0.nii.gz -d dest.nii -o warp_dest2src.nii.gz
Apply transfo source --> dest...
sct_apply_transfo -i src.nii -o src_reg.nii -d dest.nii -w warp_src2dest.nii.gz -x linear
Apply transfo dest --> source...
sct_apply_transfo -i dest.nii -o dest_reg.nii -d src.nii -w warp_dest2src.nii.gz -x linear
Generate output files...
WARNING: File spgr20to10.nii.gz already exists. Deleting it...
File created: spgr20to10.nii.gz
File created: warp_spgr20crop2spgr10crop.nii.gz
File created: spgr10crop_reg.nii.gz
File created: warp_spgr10crop2spgr20crop.nii.gz
Remove temporary files...
rm -rf tmp.150525164824
Finished! Elapsed time: 4s
To view results, type:
fslview spgr10crop.nii.gz spgr20to10.nii.gz &
fslview spgr20crop.nii.gz spgr10crop_reg.nii.gz &

are you sure it's OS-related?  did you try on other stations? with other data?
maybe it's an over-writing file issue

First, it is not a problem of memory because we tried splitting into 2D slices and applying ANTS on each slice individually: the error remains the same (see below).
Command

isct_antsRegistration --dimensionality 2 --transform Rigid[0.6] --metric MeanSquares[dest_z0013.nii,src_reg_z0013.nii,1,4] --convergence 15 --shrink-factors 1 --smoothing-sigmas 0mm --output [transform_0013] --interpolation BSpline[3]
Output

All_Command_lines_OK
Using double precision for computations.
number of levels = 1
fixed image: dest_z0013.nii
moving image: src_reg_z0013.nii
Dimension = 2
Number of stages = 1
Use Histogram Matching false
Winsorize image intensities false
Lower quantile = 0
Upper quantile = 1
Stage 1 State
Image metric = MeanSquares
Fixed image = Image (0x7ff0eb01ba40)
RTTI typeinfo:   itk::Image<double, 2u>
Reference Count: 2
Modified Time: 608
Debug: Off
Object Name:
Observers:
none
Source: (none)
Source output name: (none)
Release Data: Off
Data Released: False
Global Release Data: Off
PipelineMTime: 0
UpdateMTime: 426
RealTimeStamp: 0 seconds
LargestPossibleRegion:
Dimension: 2
Index: [0, 0]
Size: [39, 40]
BufferedRegion:
Dimension: 2
Index: [0, 0]
Size: [39, 40]
RequestedRegion:
Dimension: 2
Index: [0, 0]
Size: [39, 40]
Spacing: [0.911458, 0.911458]
Origin: [-16.5009, 8.41727]
Direction:
0.999611 6.07277e-08
0.0279047 -1
IndexToPointMatrix:
0.911103 5.53507e-08
0.025434 -0.911458
PointToIndexMatrix:
1.09757 6.66529e-08
0.0306274 -1.09714
Inverse Direction:
1.00039 6.07513e-08
0.0279156 -1
PixelContainer:
ImportImageContainer (0x7ff0eb01b930)
RTTI typeinfo:   itk::ImportImageContainer<unsigned long, double>
Reference Count: 1
Modified Time: 423
Debug: Off
Object Name:
Observers:
none
Pointer: 0x7ff0ea839e00
Container manages memory: true
Size: 1560
Capacity: 1560
 Moving image = Image (0x7ff0eb01bd70)

RTTI typeinfo:   itk::Image<double, 2u>
Reference Count: 2
Modified Time: 609
Debug: Off
Object Name:
Observers:
none
Source: (none)
Source output name: (none)
Release Data: Off
Data Released: False
Global Release Data: Off
PipelineMTime: 0
UpdateMTime: 606
RealTimeStamp: 0 seconds
LargestPossibleRegion:
Dimension: 2
Index: [0, 0]
Size: [39, 40]
BufferedRegion:
Dimension: 2
Index: [0, 0]
Size: [39, 40]
RequestedRegion:
Dimension: 2
Index: [0, 0]
Size: [39, 40]
Spacing: [0.911458, 0.911458]
Origin: [-16.5009, 8.41727]
Direction:
0.999611 6.07277e-08
0.0279047 -1
IndexToPointMatrix:
0.911103 5.53507e-08
0.025434 -0.911458
PointToIndexMatrix:
1.09757 6.66529e-08
0.0306274 -1.09714
Inverse Direction:
1.00039 6.07513e-08
0.0279156 -1
PixelContainer:
ImportImageContainer (0x7ff0eb01b750)
RTTI typeinfo:   itk::ImportImageContainer<unsigned long, double>
Reference Count: 1
Modified Time: 603
Debug: Off
Object Name:
Observers:
none
Pointer: 0x7ff0ea83d000
Container manages memory: true
Size: 1560
Capacity: 1560
 Weighting = 1
 Sampling strategy = none
 Number of bins = 32
 Radius = 4
 Sampling percentage  = 1

Transform = Rigid
Gradient step = 0.6
Update field sigma (voxel space) = 0
Total field sigma (voxel space) = 0
Update field time sigma = 0
Total field time sigma  = 0
Number of time indices = 0
Number of time point samples = 0
Registration using 1 total stages.
Stage 0
iterations = 15
convergence threshold = 1e-06
convergence window size = 10
number of levels = 1
Shrink factors (level 1 out of 1): [1, 1]
smoothing sigmas per level: [0]
using the MeanSquares metric (weight = 1)
Using default NONE metricSamplingStrategy
*** Running rigid registration ***
dyld: lazy symbol binding failed: Symbol not found: ___sincos_stret
Referenced from: /Users/slevy_local/spinalcordtoolbox/bin/osx/isct_antsRegistration
Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: ___sincos_stret
Referenced from: /Users/slevy_local/spinalcordtoolbox/bin/osx/isct_antsRegistration
Expected in: /usr/lib/libSystem.B.dylib
Trace/BPT trap: 5

can you try re-compiling ANTs (the binaries are a couple of months old) and test it again?  Also please test it on ferguson.
If it continues failing we report on ANTs forum.
thanks

re-check now with new binaries.

Works now with the new binaries.

authors: jcohenadad slevyrosetti

repo: neuropoly/spinalcordtoolbox

license: mit


text:
xrdp-sesrun only start session by Xvnc

Installed with X11rdp and Xvnc on my machine(ubuntu16.04).
I use xrdp-sesrun localhost test test 1024 768 24 to start a session.
I not find some information about it.    xrdp-sesrun just support Xvnc ??

Yes.

Solved by #1108.

authors: metalefty yingque

repo: neutrinolabs/xrdp


text:
Trying to install on Debian 11, not getting too far.

I have been attempting to get auto resizing in xrdp on Debian 10 and now 11 on my spare time for more than 2 years. It seems getting the latest xrdp to work in Debian is not really straight forward.
So due to the individual who had the brilliant idea of actually putting compile instructions in the Readme file (which was previously not there), i finally got it to compile on Debian 11, seemingly without error but now im a bit confused. It appears that its not really installed but rather just bin files available on the system. So again, no documentation anywhere i can find leaves me with little clue about what to do next.
i start the xrdp-sesman and xrdp bins using sudo from an ssh session. i try to connect from remmina and it connects, gets a black screen for  a while and does nothing.
In the logs i see:
[ERROR] sesman_data_in: scp_process_msg failed
[ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
[ERROR] There is no X server active on display 10
[ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection
in /etc/xrdp/sesman.ini everything seems normal, i can even use the sesman file that works fine with xrdp from the debian repository and nothing changes really. I have the same result with Xfce and Cinnamon on Debian 11
I have no idea what im doing really so i have virtually no ability to troubleshoot this and i cant find documentation about how make it work on debian.  I'd really appreciate if someone could help me.

Compile instructions are on the Wiki. This is linked to from the README.md. I absolutely agree that this could do with revising.
A couple of pointers:-

Right now, I'd suggest building the v0.9 branch. The devel branch is undergoing quite a bit of change at the moment, but the v0.9 branch is stable.
Connecting from Remmina can be awkward with default compile options for xrdp. See this post

With that done, you should be able to get to the xrdp login screen (just using the xrdp executable). We can then work on getting the session started.
On that point, you'll only get so far running sesman from a terminal session. in this mode, sesman will be unable to create a systemd session for the user, as you cannot create one systemd session from the context of another.
Hope that's useful.

HI, thank you for the reply. I did compile v0.9.19 successfully but that's where I got stuck. I did apply the two settings in Remmina referenced in the post you provided and thatnk you for that but Remmina still gets stuck on a black screen.
Could you elaborate on how exactly use the various bin files, seeing that they're not services, nothing seems very clear when compiling it xrdp directly. Is there a guide or something? i have no idea what I'm doing; this program is painfully ambiguous.

The build should create systemd manifests for the services. You shouldn't need to do anything special to get those.
Have you installed it with sudo make install?

im following the compile instructions on github, including the last command on the list which is   sudo make install.  All of the commands go through without any errors. I did of course had to install certain packages before ./configure would complete.
sudo apt-get install libpam0g-dev libx11-dev libxfixes-dev libxrandr-dev nasm autoconf libtool
I'm compiling .9.19, should i be using a different version or something.
So after i do   sudo make install   i do see the bin files of xrdp, xrdp-sesman etc get put onto the system, but no services for xrdp are created, neither xrdp nor for xrdp-sesman.  So i dont know if this is normal or what so i start  sudo xrdp-sesman and   sudo xrdp manually via the terminal, then i try to connect using remmina and KRDC. Both basically have the same result. they seem to connect but you get a blank or black screen, then after a minute or so it disconnects with error or returns to an xorg login window.
I have tried this procedure now on 3 computers, two of which i just freshly installed Debian 11 from scratch. Two of the PCs never had any previous version of Xrdp installed. On all 3 PCs the Xrdp from the Debian repo works perfectly. Copying the default Xrdp config from the debian repo to the new compiled one still yields the same result, it just doesnt work.
I really need auto resizing, its absolutely aweful to log in out or statically assign the resolution. I have literally been trying for 2 YEARS on and off to get auto resizing on debian 10 and now debian 11. Is it just impossible to make anything but this ancient version of xrdp without autoresizing to work on debian?  Dont any developers of xrdp even use debian?  I would really appreciate anyone who can help me get this working so i can document how to make it work; surely im not the only person in the world who uses debian and thinks VNC is rubbish.

I've just set up a clean Debian 11 VM. I'll have a look at this.
After your sudo make install, are you getting anything for systemctl status xrdp?

@thwerks - can you paste what happens when you do sudo systemctl enable --now xrdp xrdp-sesman?
The most likely reason for the error is the X server needs some configuration.

If you're trying to use the Xorg backend, make sure the path to the Xorg X server is set properly in /etc/xrdp/xrdp.ini. The comments in the file should tell you what to do.
If you're trying to use the Xvnc backend, you'll need a a VNC server installed. Use sudo apt install tigervnc-standalone-server to achive this.

In either case, there should be in an error in /etc/xrdp/xrdp-sesman.log indicating what has happened.

after entering   sudo systemctl enable --now xrdp xrdp-sesman    i get:
Job for xrdp-sesman.service failed because the control process exited with error code.
See "systemctl status xrdp-sesman.service" and "journalctl -xe" for details.
A dependency job for xrdp.service failed. See 'journalctl -xe' for details.
sesman will not start, service status reveals
(code=exited, status=1/FAILURE)
There are no errors in the log.
the   /etc/xrdp/xrdp-sesman.log   file doesnt exist, probably because the service has never successfully ran.
as far as /etc/xrdp/xrdp.ini is concerned it looks fine to me but im not exatly sure what settings need to be for xorg on debian. As i stated before, i have also tried using the xrdp.ini file that comes with xrdp from the Debian repo which obviously works with xrdo from the repo, but sadly it doesn't fix the problem with ver .9.19.
i have no idea what to try, im not even getting any error in the system log. I can only get things to somewhat work by running the file manually and even then i only get a black screen, With the service it just fails to start without even an error being produced in the log. I have no idea what to do now.

Have you got the xrdp package installed on the same machine you've tried building on?
That will probably fail, as the shared libraries won't match.
What does sudo xrdp-sesman -n say?

No, i have never installed the xrdp package on the machine in question. i have tried on other machines , but removing the package yields the same result.
sudo xrdp-sesman -n    return nothing, no error or any message is returned

It seems astonishing it doesn't create some sort of log in /var/log/xrdp-seman.log.
Try sudo strace xrdp-sesman It'll generate a bigger log, but maybe that will give more clues.

Ok i started another VM from scratch just to be sure we're on the same page.
I'm using Debian 11.4 Xfce Live which you can download here.

These are the exact commands i enter from the very fist boot:
sudo apt-get update
sudo apt-get -y dist-upgrade
sudo apt-get install -y libpam0g-dev libx11-dev libxfixes-dev libxrandr-dev nasm autoconf libtool git libssl-dev bash-completion
mkdir ~/apps
cd ~/apps
git clone https://github.com/neutrinolabs/xrdp
cd ~/apps/xrdp
./bootstrap
./configure
make
sudo make install
sudo systemctl enable --now xrdp xrdp-sesman
after entering this last command the service is started successfully. i can connect and authenticate but then i get a black screen for a few minutes, then i get an error about some error as stated earlier.

Have you now got a log in /var/log/xrdp-sesman.log?

[20220815-11:44:24] [INFO ] Received request to create Xorg session for user: user
[20220815-11:44:24] [INFO ] Terminal Server Users group is disabled, allowing authentication
[20220815-11:44:24] [INFO ] ++ created session (access granted): username user, ip 10.21.83.2
[20220815-11:44:24] [INFO ] Starting session: session_pid 1196, display :10.0, width 1546, height 908, bpp 24, client ip 10.21.83.2, user name user
[20220815-11:44:24] [INFO ] [session start] (display 10): calling auth_start_session from pid 1196
[20220815-11:44:24] [INFO ] Starting X server on display 10: Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20220815-11:44:33] [WARN ] Timed out waiting for X server on display 10 to startup
[20220815-11:44:33] [INFO ] Starting the xrdp channel server for display 10
[20220815-11:44:33] [INFO ] Session started successfully for user user on display 10
[20220815-11:44:33] [INFO ] Session in progress on display 10, waiting until the window manager (pid 1197) exits to end the session
[20220815-11:44:34] [WARN ] Timed out waiting for X server on display 10 to startup
[20220815-11:44:34] [ERROR] There is no X server active on display 10
[20220815-11:44:34] [ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection
[20220815-11:44:34] [WARN ] Window manager (pid 1197, display 10) exited quickly (1 secs). This could indicate a window manager config problem
[20220815-11:44:34] [INFO ] Calling auth_stop_session and auth_end from pid 1196
[20220815-11:44:34] [INFO ] Terminating X server (pid 1198) on display 10
[20220815-11:44:34] [INFO ] Terminating the xrdp channel server (pid 1201) on display 10
[20220815-11:44:34] [INFO ] X server on display 10 (pid 1198) returned exit code 1 and signal number 0
[20220815-11:44:34] [INFO ] xrdp channel server for display 10 (pid 1201) exit code 0 and signal number 0
[20220815-11:44:34] [INFO ] cleanup_sockets:
[20220815-11:44:34] [INFO ] Process 1196 has exited
[20220815-11:44:34] [INFO ] ++ terminated session:  username user, display :10.0, session_pid 1196, ip 10.21.83.2

Ok finally got it to work. I think what made it work was installing the package xorgxrdp and also changing "allowed_users" from "console" to "anybody" setting in /etc/X11/Xwrapper.config file. One machine did require a reboot before working, probably due to removing repo version being previously installed.

Darren
I've had great luck using xRDP install script from c-energys:
https://c-nergy.be/blog/?cat=79
Their script supports Debian & Ubuntu.
You might try it in a Debian VM.
Note the 3 optional Command line options.
Brian
On Mon, Aug 15, 2022, 7:08 AM Daren Lee @.***> wrote:

Ok finally got it to work. I think what made it work was installing the
package xorgxrdp and also changing "allowed_users" from "console" to
"anybody" setting in /etc/X11/Xwrapper.config file. One machine did require
a reboot before working, probably due to removing repo version being
previously installed.
—
Reply to this email directly, view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/2332#issuecomment-1214893643,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM23J4PBLYF3D2NPABU7VTVZIQLTANCNFSM55RZVKOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Nice Brian, I will definitely check that out and thanks for the share. I am extremely pleased to finally have auto resizing in Debian.

C-energys builds everything with latest xRDP sources
On Mon, Aug 15, 2022, 8:04 AM Daren Lee @.***> wrote:

Nice Brian, I will definitely check that out and thanks for the share. I
am extremely pleased to finally have auto resizing in Debian.
—
Reply to this email directly, view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/2332#issuecomment-1214935984,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM23JZ57OC2QHWVLGOQEL3VZIW3JANCNFSM55RZVKOA
.
You are receiving this because you commented.Message ID:
@.***>

If anyone is interested this install the latest xrdp on Debian 11. It installs necessary packages, downloads the latest get, compiles and sets xrdp to accept connections only from SSH connection (127.0.0,1) and doesnt require a reboot, it should just work after commands complete.  I can't think of many scenarios where you could safely use xrdp without an SSH tunnel so...
        sudo apt-get install -y xorgxrdp libpam0g-dev libx11-dev libxfixes-dev libxrandr-dev nasm autoconf libtool git libssl-dev bash-completion
        sudo sed 's`allowed_users=console`allowed_users=anybody`' /etc/X11/Xwrapper.config >tmp
        sudo mv tmp /etc/X11/Xwrapper.config
        mkdir ~/apps
        cd ~/apps
        git clone https://github.com/neutrinolabs/xrdp
        cd ~/apps/xrdp
        ./bootstrap
        ./configure
        make
        sudo make install
        sudo sed 's`port=3389`port=tcp://127.0.0.1:3389`' /etc/xrdp/xrdp.ini >tmp
        sudo mv tmp /etc/xrdp/xrdp.ini
        sudo systemctl enable --now xrdp xrdp-sesman

authors: bmullan matt335672 thwerks


text:
Fails to parse

When I use the example from the repo to run groc, it works fine. However, I use load-grunt-tasks to load my task configurations from a separate file and when I define it there, I get errors.
Here is the trace:
! Failed to parse doc tags C:\dev\server\wamp\www\testApp\app\scripts\app.js: Cannot read property '1' of null
TypeError: Cannot read property '1' of null
at Object.module.exports.DOC_TAGS.param.parseValue (C:\dev\server\wamp\www\testApp\node_modules\grunt-groc\node_modules\groc\lib\doc_tags.coffee:124:7)
at Object.module.exports.Utils.parseDocTags (C:\dev\server\wamp\www\testApp\node_modules\grunt-groc\node_modules\groc\lib\utils.coffee:637:39)
at Default.module.exports.Base.renderFile (C:\dev\server\wamp\www\testApp\node_modules\grunt-groc\node_modules\groc\lib\styles\base.coffee:27:11)
at C:\dev\server\wamp\www\testApp\node_modules\grunt-groc\node_modules\groc\lib\project.coffee:83:15
at fs.js:271:14
at Object.oncomplete (fs.js:107:15)
Here is my task config:
module.exports = {
    javascript: {
        files: {src: ["<%=pkg.directories.dev_root %><%=pkg.directories.js %>*.js"]},
        options: {
            "out": "<%=pkg.directories.doc_root %>"
        }
    }
};

This is not an issue with configuration, but rather an issue that I see as a Groc flaw. If a doc comment does not contain a data type along with the parameter descriptions, this error is thrown. For example, the following doc comment will cause the error above to be thrown:
/**
 * @param e Some event object
 */
someFunc: function (e) {
    .....code.....
}

Since "e" here is not assigned a data type, I get the ! Failed to parse.... error, with no details on where/why/what this error is.
This should be reduced to a WARNING severity level and continue on in my opinion. Or, at the very least, a descriptive error message should explain where the error occurred because right now "property 1 of null" inside some obscure loop in the Groc inner-workings is not troubleshootable. Though it looks to me like there's just no catch for a possible check against null, so try-catch might be the intended solution here, just not implemented yet. Hope this helps!

I can confirm this error, in my code any of these @param will let groc fail:
/**
 * @param anything
 */

with:
  Generating documentation...
! Failed to parse doc tags /home/julius/server/lib/Auth/Protocol.js: Cannot read property '1' of null
   TypeError: Cannot read property '1' of null
    at Object.module.exports.DOC_TAGS.param.parseValue (/usr/lib/node_modules/groc/lib/doc_tags.coffee:124:7)
    at Object.module.exports.Utils.parseDocTags (/usr/lib/node_modules/groc/lib/utils.coffee:641:39)
    at Default.module.exports.Base.renderFile (/usr/lib/node_modules/groc/lib/styles/base.coffee:28:11)
    at /usr/lib/node_modules/groc/lib/project.coffee:103:15
    at fs.js:272:14
    at Object.oncomplete (fs.js:108:15)

repo: nevir/groc


text:
Typo in file name: axiios-logger-config.ts

File path: axios-logger/src/config/axiios-logger-config.ts
axiios-logger-config.ts should be axios-logger-config.ts

Thanks for noticing this. I will look into it later. If you want, you are welcome to make a Pull Request for this :)

authors: MungoWang azakordonets


text:
Add button to allow trigger update source meta

https://github.com/biothings/biothings.api/issues/231

This PR implemented a feature called: update_metadata, it used to quickly update the source metadata without re-dump, re-upload.
a "Update Metadata" button added to uploader tag in the detail source page

When click to the button, the studio will fetch the current and new metadata from the backend, and show them to user to verify the change

After click update, a success modal will show.

If the current and new metadata are same, nothing is changed.


text:
hashids scala-way

Hi, newhoggy!
I'v been using Java version of hashids for some time in my scala project and when I found your scala port, I was eager to switch and use native library. But then I found that code didn't differ from java version... All those vars ... So I went with a rewrite, to make it more into scala-way.
Also I found and fixed couple things:

Decode function result check with encode function. Returing empty result in case of buggy decode function isn't good idea. Decode should be working fine without double checks.
Implicit functions in separate file. Those naturally fit into complanion object next to apply functions.
Trying to fix incorrect alphabet in constructor: if it's incorrect, it should be clearly communicated back to programmer. Otherwise alphabet is different from what library client thinks.

Hope this is helpfull.
PS. One other thing i dislike is that your repo is a fork of java's one. Scala deserves it's own repo, I think. It's not possible to pull updates and publish pull requests to java repo anyway.

@ancane @newhoggy is this going to be merged in or should it be closed?

Merged.  But bear with me a moment while I upgrade dependencies and the build and perform some general cleanup before publishing.

Great, thanks.

Latest code has been published.  Note that, the code is now being published to a different repository.

authors: ancane ilanbiala newhoggy

repo: newhoggy/hashids-scala


text:
[Theme] Replace all instrumentation with tessen

We're fully removing events fired by the browser agent and replacing them with tessen actions.
Acceptance Criteria

[ ] Remove useInstrumentedData hook (check for any uses in the opensource/dev/docs sites or theme first but I didn’t find any)
[ ] remove all browser agent page actions from the theme
[ ] Edit useInstrumentedHandler code to remove browser option/fallback (we don’t need to pass an agent argument anymore)

[ ] Check and update the use of useInstrumentedHandler in any theme components
[ ] Check and update the instrumentation prop on any theme components
[ ] Add warnings to useInstrumentedHandler for malformed category or event names

eventName is camelCase
category is Title Case

[ ] Add warnings to createtessen.js for malformed category or event names
[ ] Update any tests affected
[ ] Update any documentation/wiki references to the browser events. Remove the documentation for useInstrumentedData
[ ] Update any dashboards tracking browser events from theme components (here are the most important)

[DevEn] External I/O & Quickstarts Ecosystem
New Relic I/O Program Dashboard
[DevEn] Docs Ecosystem

@roadlittledawn mentioned that we need to verify the theme is not sending any browser agent page actions..

looks like the theme sends two PageAction actions called:

navInteraction
swiftypeSearch_input

Leaving this in open for now, once all the sites are updated with the new theme we'll do one final pass to check the charts are all correct

We're going to update the dashboards as we complete the other tickets.

authors: LizBaker jpvajda roadlittledawn rudouglas zstix

repo: newrelic/gatsby-theme-newrelic


text:
[DRI action] Reenable pre-release tests in Jenkins

See https://docs.google.com/document/d/1k1grPrOxX00Wyh78lBx1V5Xu5v7rHcmFv3uYtcuOtz4/edit

URL was updated on Jenkins. We need to check if tests continue to run & pass.
Align with CoreInt on the integration related tests if failing. OHIs tests were already "migrated" to Github.

Agent installation tests have been restored on staging
Added new case: verifying service keeps running after upgrade
Removed old newrelic-infra-integrations package from the suite
Integration tests are disabled, do these belong to CoreInt or should CAOS restore these as well?

In my understanding, we do test integrations independently in the integrations pipelines. Any concern on disabling integration tests here @davidbrota ?

CoreInt migrated installation tests into GHA pipeline AFAIK

Yes, integrations are released independently. Installation tests can be triggered manually, but they also run automatically on a hourly basis. They use staging environment, and I think we should move cron'ed ones (hourlies) to production env. Staging  env fits better in the use case for manual trigger (or gated pre-release CI).

We are already testing integrations locally and remotely using the staging and prod repos for apt, yum and zypp.

authors: brushknight davidbrota mmorel-nr varas

repo: newrelic/infrastructure-agent


text:
Added metadata for python page

Previous:
Title:
Python | New Relic Instant Observability
Description:
New Relic's instant observability quickstart boasts alerts, event loop diagnostics, and multiple customizable dashboards to detect and resolve issues before they impact end-users.
Now:
Title:
Python Application Performance Monitoring | New Relic
Description:
Python monitoring tool by New Relic helps business users and developers monitor Python application performance
Observation
I made changes on quickstart-metadata.json and then I have executed the code. But on http://localhost:8000/python/986df593-98db-485b-8e8c-dd866fa28813, I am not able to observe the updated title and description. Kindly guide me if I am going wrong somewhere.
Thank you. 🙂

Hey @pkosanam, I'm not sure why you aren't seeing the changes locally. I am able to see them in the preview!

authors: aswanson-nr pkosanam

repo: newrelic/instant-observability-website


text:
Update Artifact Actions to Newer Versions

Overview

Update artifact upload/download actions to latest version to fix issues with new Github functionality breaking existing actions.
Update code coverage action after previous version was deprecated

Add required security token for new version to function

Add missing firestore dependency graph link for code coverage action

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.68%. Comparing base (6fd639d) to head (fb0c2e6).
Report is 323 commits behind head on main.

:exclamation: Current head fb0c2e6 differs from pull request most recent head 1cd2400. Consider uploading reports for the commit 1cd2400 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1125      +/-   ##
==========================================
+ Coverage   81.15%   81.68%   +0.53%
==========================================
  Files         190      192       +2
  Lines       19747    21303    +1556
  Branches     3468     3707     +239
==========================================
+ Hits        16025    17402    +1377
- Misses       2732     2821      +89
- Partials      990     1080      +90

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

authors: TimPansino codecov-commenter

repo: newrelic/newrelic-python-agent


text:
feat: validate token lambda (#37)

feat: added validate token lambda definition

feat: added lambda template for validate token handler

refactor: changed the handler name

chore: added dynamoose and serverless-iam-roles-per-function

feat: added read only role for validate token lambda

feat: added role per function to validate token

feat: added validation attempts model

feat: added basic query for dynamodb to test the db settings

chore: added new variables to config for the aurora db

feat: added database types

feat: added select all data query

chore: added aws sdk

feat: setup the lambda permissions

refactor: removed unused model

feat: added database record type

feat: created database context for validate token

chore: added aurora db dummy fields to test env

refactor: disabled including result metadata

feat: added db method templates

chore: updated packages

feat: added get record by token

fix: wrong table name

refactor: clean up database types

feat: added get validation by account id

feat: extends lambda error responses

feat: added validate token lambda

refactor: improved returned response from validate token lambda

 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.

 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.

authors: CLAassistant norbertsuski

repo: newrelic/nr-ngo-validation-serverless


text:
URLs open in AboutCode Manager page

Description
When a user clicks a URL, the resulting page is loaded in the same window as the AboutCode Manager had just occupied. This is an obvious problem, as there is no was to go "Back" to AboutCode Manager after the clicked URL loads.
We should probably have URLs open in the user's default browser, or in a separate pop-up window.
Before Pick:

After Pick:

merged #237, closing.

repo: nexB/aboutcode-manager


text:
Vpcs

commit 0e7650ec86c4a324e6d0a7a5740161b7eddce8af (HEAD -> vpcs, chirino/vpcs)
Author: Hiram Chirino hiram@hiramchirino.com
Date:   Wed Nov 1 14:58:15 2023 -0400
refactor: split up the Organization model into an Organization and VPC so that an organization can contain multiple VPC resources.

Mostly complies but tests need to be fixed.

Signed-off-by: Hiram Chirino <hiram@hiramchirino.com>

commit 33e5ade244ba89ff7f83cdef661bd1696fbf8323
Author: Hiram Chirino hiram@hiramchirino.com
Date:   Tue Oct 31 17:14:44 2023 -0400
apiserver: squash all previous migrations.

I did "ready for review" so that the e2e job would start running on the branch.

authors: chirino russellb

repo: nexodus-io/nexodus


text:
Clickable text drawings don't work

When I create the text drawings after the plugin this message appears:
[textdraw.streamer] DynamicPlayerTextDrawShow: First create the player textdraw.
[textdraw.streamer] DynamicPlayerTextDrawHide: First create the player textdraw.

But textdraws inside textdraw-streamer callbacks respond correctly.
When I create the text drawings before the plugin the clickable textdraws don't work.

So, I wonder, even if the message "first create the player textdraw" appears, if I click and it responds to the callback, does it mean it's working? And I want to know if I'm exceeding the limit or making the message disappear to make it work properly.

Message warning means it's not working properly. You must first create a text drawing with CreatePlayerTextDraw. Can I see your codes and your library order?

#include <a_samp>
#include <a_mysql>
#include <streamer>
#include <sscanf2>
#include <foreach>
#include <YSI\y_timers>
#include <YSI\y_utils>
#include <YSI\y_ini>
#include <YSI\y_hooks>
#include <mapandreas>
#include <colandreas>
#include <Pawn.RakNet>
#include <Pawn.CMD>
#include <textdraw-streamer> // with the include here everything works correctly but when I place the plugin afterwards I can't click on the textdraws

// Textdraws

#include "textdraws/main_menu.pwn"
#include "textdraws/compass.pwn"
#include "textdraws/hud.pwn"
#include "textdraws/clock.pwn"
#include "textdraws/actions.pwn"

Version 1.6.2 worked fine for me but I want to keep up to date

There may be a hooking problem.

Can you try without the hook method?
Using only native.
Example:
CreatePlayerTextDraw -> CreateDynamicPlayerTextDraw

it was not solved

Would you like to share your game mod so I can quickly identify the problem.

Could you tell me what current features correspond to those of version 1.6.2?

In v1.6.2 the callbacks are different, you can look it up in textdraw-streamer.inc

https://github.com/nexquery/samp-textdraw-streamer/blob/070d11a88c07f4d77ebc87713e10b8ea1246fe93/textdraw-streamer.inc#L75

thanks

Can you add me on discord?
If you share your game mod, I can quickly identify the problem.
Discord: Nexor#4730

solved
thanks @nexquery

authors: knightsamp nexquery

repo: nexquery/samp-textdraw-streamer


text:
Fix variable name bug that shows up when library is executed without …

…sufficient privilege to access docker daemon

Good catch, thanks!

authors: markAcomm nextrevision

repo: nextrevision/ansible-swarm-playbook