Deploying Nextjs app on AWS: Build fails

Hi,
I am trying to deploy my nextjs app on aws through github repository. But the build is failing and giving me below pasted message. In terms of aws services, I am using auth, appsync, s3 storage. The whole app is working fine on localhost but I need to deploy it to aws for the whole team.
Can someone please tell me what am I doing wrong? I have pasted structure of my package.json.
My package.json looks like:
{
"name": "data-app",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build & next export",
"start": "next start",
"lint": "next lint"
},
"dependencies": {
"@aws-amplify/ui-react": "^1.2.26",
"aws-amplify": "^4.3.14",
"next": "12.0.10",
"react": "17.0.2",
"react-dom": "17.0.2",
"react-markdown": "^8.0.0",
"react-router-dom": "^6.2.2",
"react-simplemde-editor": "^5.0.2",
"uuid": "^8.3.2"
},
"devDependencies": {
"autoprefixer": "^10.4.2",
"eslint": "8.9.0",
"eslint-config-next": "12.0.10",
"postcss": "^8.4.6",
"tailwindcss": "^3.0.23"
}
}
Error message from build in aws amplify:
2022-03-07T19:43:50.544Z [INFO]: WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-03-07T19:43:50.553Z [INFO]: npm
2022-03-07T19:43:50.553Z [INFO]: WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-03-07T19:43:50.553Z [INFO]:
2022-03-07T19:43:50.609Z [INFO]: # Done patching NPM package '@aws-amplify/cli' to version 7.6.23
2022-03-07T19:43:50.616Z [INFO]: # Retrieving cache...
2022-03-07T19:43:50.649Z [INFO]: # Extracting cache...
2022-03-07T19:43:50.659Z [INFO]: # Extraction completed
# Starting phase: build
2022-03-07T19:43:56.496Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2022-03-07T19:43:57.964Z [INFO]: Amplify AppID found: d1gpeca41jkctg. Amplify App name is: demo-next-app
2022-03-07T19:43:58.120Z [INFO]: Adding backend environment main to AWS Amplify app: d1gpeca41jkctg
2022-03-07T19:43:58.180Z [WARNING]: - Initializing project in the cloud...
2022-03-07T19:44:03.587Z [INFO]:
2022-03-07T19:44:03.589Z [INFO]: CREATE_IN_PROGRESS amplify-dataapp-main-194357 AWS::CloudFormation::Stack Mon Mar 07 2022 19:43:58 GMT+0000 (Coordinated Universal Time) User Initiated
2022-03-07T19:44:08.584Z [INFO]:
2022-03-07T19:44:08.586Z [INFO]: CREATE_IN_PROGRESS DeploymentBucket AWS::S3::Bucket Mon Mar 07 2022 19:44:04 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UnauthRole       AWS::IAM::Role  Mon Mar 07 2022 19:44:04 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS AuthRole         AWS::IAM::Role  Mon Mar 07 2022 19:44:04 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UnauthRole       AWS::IAM::Role  Mon Mar 07 2022 19:44:05 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS DeploymentBucket AWS::S3::Bucket Mon Mar 07 2022 19:44:05 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS AuthRole         AWS::IAM::Role  Mon Mar 07 2022 19:44:05 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
2022-03-07T19:44:23.580Z [INFO]:
2022-03-07T19:44:23.584Z [INFO]: CREATE_COMPLETE UnauthRole AWS::IAM::Role Mon Mar 07 2022 19:44:18 GMT+0000 (Coordinated Universal Time)
CREATE_COMPLETE AuthRole   AWS::IAM::Role Mon Mar 07 2022 19:44:20 GMT+0000 (Coordinated Universal Time)
2022-03-07T19:44:28.593Z [INFO]:
2022-03-07T19:44:28.594Z [INFO]: CREATE_COMPLETE DeploymentBucket AWS::S3::Bucket Mon Mar 07 2022 19:44:27 GMT+0000 (Coordinated Universal Time)
2022-03-07T19:44:33.598Z [INFO]:
2022-03-07T19:44:33.599Z [INFO]: CREATE_COMPLETE amplify-dataapp-main-194357 AWS::CloudFormation::Stack Mon Mar 07 2022 19:44:29 GMT+0000 (Coordinated Universal Time)
2022-03-07T19:44:58.736Z [WARNING]: ✔ Successfully created initial AWS cloud resources for deployments.
2022-03-07T19:44:58.869Z [WARNING]: - Uploading files...
2022-03-07T19:44:58.936Z [WARNING]: - Uploading files...
2022-03-07T19:44:59.029Z [WARNING]: - Uploading files...
2022-03-07T19:44:59.286Z [WARNING]: - Initializing your environment: main
2022-03-07T19:44:59.286Z [WARNING]: ✔ Initialized provider successfully.
2022-03-07T19:44:59.686Z [INFO]: ⚠  WARNING: your GraphQL API currently allows public create, read, update, and delete access to all models via an API Key. To configure PRODUCTION-READY authorization rules, review: https://docs.amplify.aws/cli/graphql/authorization-rules
2022-03-07T19:45:00.124Z [INFO]: GraphQL schema compiled successfully.
Edit your schema at /codebuild/output/src812440592/src/demo-next-app/amplify/backend/api/dataapp/schema.graphql or place .graphql files in a directory at /codebuild/output/src812440592/src/demo-next-app/amplify/backend/api/dataapp/schema
2022-03-07T19:45:00.133Z [WARNING]: - Building resource api/dataapp
2022-03-07T19:45:00.251Z [INFO]: ⚠  WARNING: your GraphQL API currently allows public create, read, update, and delete access to all models via an API Key. To configure PRODUCTION-READY authorization rules, review: https://docs.amplify.aws/cli/graphql/authorization-rules
2022-03-07T19:45:00.573Z [INFO]: GraphQL schema compiled successfully.
Edit your schema at /codebuild/output/src812440592/src/demo-next-app/amplify/backend/api/dataapp/schema.graphql or place .graphql files in a directory at /codebuild/output/src812440592/src/demo-next-app/amplify/backend/api/dataapp/schema
2022-03-07T19:45:00.575Z [WARNING]: - Building resource auth/dataapp1a2515b8
2022-03-07T19:45:00.626Z [WARNING]: - Building resource storage/postimages
2022-03-07T19:45:00.726Z [WARNING]: - Uploading files...
2022-03-07T19:45:01.048Z [WARNING]: - Updating resources in the cloud. This may take a few minutes...
2022-03-07T19:45:07.044Z [INFO]:
2022-03-07T19:45:07.047Z [INFO]: UPDATE_IN_PROGRESS amplify-dataapp-main-194357 AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:01 GMT+0000 (Coordinated Universal Time) User Initiated
2022-03-07T19:45:12.094Z [INFO]:
2022-03-07T19:45:12.095Z [INFO]: CREATE_IN_PROGRESS authdataapp1a2515b8            AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:09 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS hostingamplifyhosting          AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:09 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UpdateRolesWithIDPFunctionRole AWS::IAM::Role             Mon Mar 07 2022 19:45:09 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS storagepostimages              AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:10 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UpdateRolesWithIDPFunctionRole AWS::IAM::Role             Mon Mar 07 2022 19:45:10 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS hostingamplifyhosting          AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:10 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS authdataapp1a2515b8            AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:10 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_IN_PROGRESS storagepostimages              AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:11 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
2022-03-07T19:45:12.141Z [INFO]:
2022-03-07T19:45:12.141Z [INFO]: CREATE_IN_PROGRESS amplify-dataapp-main-194357-storagepostimages-1X38OFDV31YO2 AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:11 GMT+0000 (Coordinated Universal Time) User Initiated
2022-03-07T19:45:12.246Z [INFO]:
2022-03-07T19:45:12.247Z [INFO]: CREATE_IN_PROGRESS amplify-dataapp-main-194357-authdataapp1a2515b8-1QSXZDQAW1VMM AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:10 GMT+0000 (Coordinated Universal Time) User Initiated
2022-03-07T19:45:12.341Z [INFO]:
2022-03-07T19:45:12.341Z [INFO]: CREATE_IN_PROGRESS amplify-dataapp-main-194357-hostingamplifyhosting-1OBVZY28830J9 AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:10 GMT+0000 (Coordinated Universal Time) User Initiated
2022-03-07T19:45:17.321Z [INFO]:
2022-03-07T19:45:17.322Z [INFO]: CREATE_IN_PROGRESS AmplifyBranch AWS::Amplify::Branch Mon Mar 07 2022 19:45:15 GMT+0000 (Coordinated Universal Time)
2022-03-07T19:45:22.053Z [INFO]:
2022-03-07T19:45:22.055Z [INFO]: CREATE_FAILED hostingamplifyhosting          AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:21 GMT+0000 (Coordinated Universal Time) Embedded stack arn:aws:cloudformation:us-east-1:984348161056:stack/amplify-dataapp-main-194357-hostingamplifyhosting-1OBVZY28830J9/193e6fd0-9e4f-11ec-9f3c-0ab6a86326e3 was not successfully created: The following resource(s) failed to create: [AmplifyBranch].
CREATE_FAILED UpdateRolesWithIDPFunctionRole AWS::IAM::Role             Mon Mar 07 2022 19:45:21 GMT+0000 (Coordinated Universal Time) Resource creation cancelled
2022-03-07T19:45:22.133Z [INFO]:
2022-03-07T19:45:22.134Z [INFO]: CREATE_FAILED AmplifyBranch                                                   AWS::Amplify::Branch       Mon Mar 07 2022 19:45:18 GMT+0000 (Coordinated Universal Time) Resource handler returned message: "Invalid request provided: Failed to create branch. The branch main already exists for the app d1gpeca41jkctg (Service: Amplify, Status Code: 400, Request ID: 2b88d833-130b-42cc-9f99-0a60c17c1613, Extended Request ID: null)" (RequestToken: da4bb552-3242-556b-8791-aefc22d2e96f, HandlerErrorCode: InvalidRequest)
CREATE_FAILED amplify-dataapp-main-194357-hostingamplifyhosting-1OBVZY28830J9 AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:19 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to create: [AmplifyBranch].
2022-03-07T19:45:22.224Z [INFO]:
2022-03-07T19:45:22.225Z [INFO]: CREATE_IN_PROGRESS S3Bucket AWS::S3::Bucket Mon Mar 07 2022 19:45:17 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS S3Bucket AWS::S3::Bucket Mon Mar 07 2022 19:45:18 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
2022-03-07T19:45:22.329Z [INFO]:
2022-03-07T19:45:22.330Z [INFO]: CREATE_IN_PROGRESS UserPool AWS::Cognito::UserPool Mon Mar 07 2022 19:45:18 GMT+0000 (Coordinated Universal Time)
CREATE_IN_PROGRESS UserPool AWS::Cognito::UserPool Mon Mar 07 2022 19:45:20 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
CREATE_COMPLETE    UserPool AWS::Cognito::UserPool Mon Mar 07 2022 19:45:21 GMT+0000 (Coordinated Universal Time)
2022-03-07T19:45:22.442Z [INFO]:
2022-03-07T19:45:22.443Z [INFO]: CREATE_FAILED authdataapp1a2515b8 AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:21 GMT+0000 (Coordinated Universal Time) Resource creation cancelled
CREATE_FAILED storagepostimages   AWS::CloudFormation::Stack Mon Mar 07 2022 19:45:21 GMT+0000 (Coordinated Universal Time) Resource creation cancelled
2022-03-07T19:45:27.082Z [INFO]:
at IncomingMessage.emit (events.js:412:35)
at IncomingMessage.emit (domain.js:475:12)
at endReadableNT (internal/streams/readable.js:1334:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
code: 'ResourceNotReady',
retryable: false,
time: 2022-03-07T19:48:02.665Z,
statusCode: 200,
retryDelay: 30000
}
2022-03-07T19:48:07.695Z [ERROR]: !!! Build failed
2022-03-07T19:48:07.696Z [ERROR]: !!! Non-Zero Exit Code detected
2022-03-07T19:48:07.696Z [INFO]: # Starting environment caching...
2022-03-07T19:48:07.696Z [INFO]: # Environment caching completed
My backend deployment gives me these information:

Can someone please help me with this? Or just guide me from where to start? I will really appreciate any direction, any guidance.
Thanks,
IP

Hi,
I am updating my question. Sorry for any inconvenience. But I found what was the issue and why I was getting backend error. My configuration was not correct, so I rectified that. But my build is still failing and I am getting frontend error.
Please see below pasted error:. As you can see from the error, it suggests building the app. I tried that too, but it didn't help.
My appid is d2jqfqeg91useg. My region is 'us-east-1'.
data-app@ build /codebuild/output/src755519296/src/demo-next-app
> next build & next export
2022-03-07T20:37:08.752Z [INFO]: Attention: Next.js now collects completely anonymous telemetry regarding usage.
2022-03-07T20:37:08.752Z [INFO]: This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
2022-03-07T20:37:08.888Z [INFO]: info  - using build directory: /codebuild/output/src755519296/src/demo-next-app/.next
2022-03-07T20:37:08.890Z [WARNING]: Error: Could not find a production build in the '/codebuild/output/src755519296/src/demo-next-app/.next' directory. Try building your app with 'next build' before starting the static export. https://nextjs.org/docs/messages/next-export-no-build-id
at /codebuild/output/src755519296/src/demo-next-app/node_modules/next/dist/export/index.js:158:19
at async Span.traceAsyncFn (/codebuild/output/src755519296/src/demo-next-app/node_modules/next/dist/trace/trace.js:75:20)
2022-03-07T20:37:08.906Z [WARNING]: npm
2022-03-07T20:37:08.906Z [WARNING]: ERR! code ELIFECYCLE
npm ERR! errno 1
2022-03-07T20:37:08.911Z [WARNING]: npm
2022-03-07T20:37:08.911Z [WARNING]: ERR! data-app@ build: next build & next export
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the data-app@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-03-07T20:37:08.919Z [WARNING]:
2022-03-07T20:37:08.919Z [WARNING]: npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-03-07T20_37_08_911Z-debug.log
2022-03-07T20:37:08.919Z [HELP]: Outputting the npm debug log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/root/.nvm/versions/node/v14.18.1/bin/node',
1 verbose cli   '/root/.nvm/versions/node/v14.18.1/bin/npm',
1 verbose cli   'run',
1 verbose cli   'build'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle data-app@~prebuild: data-app@
6 info lifecycle data-app@~build: data-app@
7 verbose lifecycle data-app@~build: unsafe-perm in lifecycle true
8 verbose lifecycle data-app@~build: PATH: /root/.nvm/versions/node/v14.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/codebuild/output/src755519296/src/demo-next-app/node_modules/.bin:/usr/local/rvm/gems/ruby-2.4.6/bin:/usr/local/rvm/gems/ruby-2.4.6@global/bin:/usr/local/rvm/rubies/ruby-2.4.6/bin:/usr/local/rvm/bin:/root/.nvm/versions/node/v14.18.1/bin:/root/.local/bin:/root/.local/bin:/root/.local/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/.dotnet/tools
9 verbose lifecycle data-app@~build: CWD: /codebuild/output/src755519296/src/demo-next-app
10 silly lifecycle data-app@~build: Args: [ '-c', 'next build & next export' ]
11 silly lifecycle data-app@~build: Returned: code: 1  signal: null
12 info lifecycle data-app@~build: Failed to exec build script
13 verbose stack Error: data-app@ build: next build & next export
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter. (/root/.nvm/versions/node/v14.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:400:28)
13 verbose stack     at ChildProcess. (/root/.nvm/versions/node/v14.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:400:28)
13 verbose stack     at maybeClose (internal/child_process.js:1058:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
14 verbose pkgid data-app@
15 verbose cwd /codebuild/output/src755519296/src/demo-next-app
16 verbose Linux 4.14.252-195.483.amzn2.x86_64
17 verbose argv "/root/.nvm/versions/node/v14.18.1/bin/node" "/root/.nvm/versions/node/v14.18.1/bin/npm" "run" "build"
18 verbose node v14.18.1
19 verbose npm  v6.14.15
20 error code ELIFECYCLE
21 error errno 1
22 error data-app@ build: next build & next export
22 error Exit status 1
23 error Failed at the data-app@ build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
2022-03-07T20:37:08.923Z [ERROR]: !!! Build failed
2022-03-07T20:37:08.923Z [ERROR]: !!! Non-Zero Exit Code detected
2022-03-07T20:37:08.923Z [INFO]: # Starting environment caching...
2022-03-07T20:37:08.924Z [INFO]: # Environment caching completed
Terminating logging...
2022-03-07T20:37:11.548Z [INFO]: info  - Checking validity of types...
./pages/about.js
10:13  Warning: Do not use . Use Image from 'next/image' instead. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
./pages/contact.js
124:11  Warning: Do not use . Use Image from 'next/image' instead. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
./pages/create-post.js
72:17  Warning: Do not use . Use Image from 'next/image' instead. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
72:17  Warning: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images.  jsx-a11y/alt-text
./pages/create-posta.js
130:21  Warning: Do not use . Use Image from 'next/image' instead. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
130:21  Warning: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images.  jsx-a11y/alt-text
./pages/edit-post/[id].js
90:9  Warning: Do not use . Use Image from 'next/image' instead. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
90:9  Warning: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images.  jsx-a11y/alt-text
./pages/edit-posta/[id].js
92:9  Warning: Do not use . Use Image from 'next/image' instead. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
92:9  Warning: img elements must have an alt prop, either with meaningful text, or an empty string for decorative images.  jsx-a11y/alt-text
./pages/my-postsa.js
45:6  Warning: React Hook useEffect has a missing dependency: 'fetchPosts'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
info  - Creating an optimized production build...

npm run build gives me following error:
Error: Could not find a production build in the 'C:\Users\sh55451\Documents\UGA\brookdodo\data-app.next' directory. Try building your app with 'next build' before starting the static export. https://nextjs.org/docs/messages/next-export-no-build-id
at C:\Users\sh55451\Documents\UGA\brookdodo\data-app\node_modules\next\dist\export\index.js:158:19
at async Span.traceAsyncFn (C:\Users\sh55451\Documents\UGA\brookdodo\data-app\node_modules\next\dist\trace\trace.js:75:20)

Hi @igloopigloo 👋🏽 we are looking into this, will update with more information shortly

There's a typo in your package.json.
Replace "build": "next build & next export", with "build": "next build && next export", (logical AND)

Hi,
That did fixed the issue, but now when I am deploying it to aws, it is throwing backend error. Please see below pasted message. I googled the error and did following steps:
npm cache clean --force
delete node_modules and package-lock.json
npm install
npm start
npm run dev
Again the whole thing is working fine on localhost but deployment is failing
The error is:
2022-03-09T18:50:17.846Z [WARNING]: ERR! code ELIFECYCLE
npm ERR! errno 1
2022-03-09T18:50:17.849Z [WARNING]: npm
2022-03-09T18:50:17.849Z [WARNING]: ERR! data-app@ build: next build && next export
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the data-app@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-03-09T18:50:17.854Z [WARNING]:
2022-03-09T18:50:17.854Z [WARNING]: npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-03-09T18_50_17_849Z-debug.log
2022-03-09T18:50:17.854Z [HELP]: Outputting the npm debug log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/root/.nvm/versions/node/v14.18.1/bin/node',
1 verbose cli   '/root/.nvm/versions/node/v14.18.1/bin/npm',
1 verbose cli   'run',
1 verbose cli   'build'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle data-app@~prebuild: data-app@
6 info lifecycle data-app@~build: data-app@
7 verbose lifecycle data-app@~build: unsafe-perm in lifecycle true
8 verbose lifecycle data-app@~build: PATH: /root/.nvm/versions/node/v14.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/codebuild/output/src736534747/src/demo-next-app/node_modules/.bin:/usr/local/rvm/gems/ruby-2.4.6/bin:/usr/local/rvm/gems/ruby-2.4.6@global/bin:/usr/local/rvm/rubies/ruby-2.4.6/bin:/usr/local/rvm/bin:/root/.nvm/versions/node/v14.18.1/bin:/root/.local/bin:/root/.local/bin:/root/.local/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/.dotnet/tools
9 verbose lifecycle data-app@~build: CWD: /codebuild/output/src736534747/src/demo-next-app
10 silly lifecycle data-app@~build: Args: [ '-c', 'next build && next export' ]
11 silly lifecycle data-app@~build: Returned: code: 1  signal: null
12 info lifecycle data-app@~build: Failed to exec build script
13 verbose stack Error: data-app@ build: next build && next export
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter. (/root/.nvm/versions/node/v14.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:400:28)
13 verbose stack     at ChildProcess. (/root/.nvm/versions/node/v14.18.1/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:400:28)
13 verbose stack     at maybeClose (internal/child_process.js:1058:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
14 verbose pkgid data-app@
15 verbose cwd /codebuild/output/src736534747/src/demo-next-app
16 verbose Linux 4.14.252-195.483.amzn2.x86_64
17 verbose argv "/root/.nvm/versions/node/v14.18.1/bin/node" "/root/.nvm/versions/node/v14.18.1/bin/npm" "run" "build"
18 verbose node v14.18.1
19 verbose npm  v6.14.15
20 error code ELIFECYCLE
21 error errno 1
22 error data-app@ build: next build && next export
22 error Exit status 1
23 error Failed at the data-app@ build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
2022-03-09T18:50:17.858Z [ERROR]: !!! Build failed
2022-03-09T18:50:17.858Z [ERROR]: !!! Non-Zero Exit Code detected
2022-03-09T18:50:17.858Z [INFO]: # Starting environment caching...
2022-03-09T18:50:17.859Z [INFO]: # Environment caching completed
Can you please help me out.
Thanks

You said your app runs locally but can you ensure that it builds locally as well. If it cannot build locally then the issue is most likely with the configuration of the app.

Please


Fixes for CMD check

I think this is the most elegant (least ugly) way of fixing this. We don't change the actual upstream code but instead mask the illegal functions with the corresponding legal alternatives.

Ah nice!


Add GitHub Action to perform regression testing with Apache Calcite bytecode

@n1hility , I think the PR is ready. Well, regression jobs fail, however, they highlight the issues.

@n1hility , I think the PR is ready. Well, regression jobs fail, however, they highlight the issues.

@vlsi I fixed a few more issues that were reported in the logs here, but I was having trouble reproducing the failure locally (downloading the classes that were built and then running jandex on them had no issues). Since this error looks like one of the ones that was fixed, I thought I saw a caching issue but I verified at least part of the build is picking up changes. Not sure if there is anything special about the usage of your gradle plugin but it didn't look like it glancing at the source. Anyway I need to crash but let me know if you spot anything.

@vlsi I fixed a few more issues that were reported in the logs here, but I was having trouble reproducing the failure locally (downloading the classes that were built and then running jandex on them had no issues). Since this error looks like one of the ones that was fixed, I thought I saw a caching issue but I verified at least part of the build is picking up changes. Not sure if there is anything special about the usage of your gradle plugin but it didn't look like it glancing at the source. Anyway I need to crash but let me know if you spot anything.

Oh, let me see.

Oh, let me see.

@n1hility ,

Gradle does not cache the results of failure tasks (it is not implemented in the current Gradle versions)
I can reproduce Required class information is missing failures locally.

For instance, I download calcite-work.tgz, I take calcite/core/build/classes/java/main/org/apache/calcite/adapter/clone/ArrayTable$1.class file (1477 bytes), and I run the following:
public class TestClassBounds {
    @Test
    public void classBounds() throws IOException {
        Indexer indexer = new Indexer();
        ClassInfo info = indexer.index(new FileInputStream("/tmp/ArrayTable$1.class"));
        System.out.println("info = " + info);
        Index index = indexer.complete();
        System.out.println("subclasses");
        index.printSubclasses();
        System.out.println("annotations");
        index.printAnnotations();
    }
}

The error can be reproduced as follows: https://github.com/wildfly/jandex/issues/92
Are you sure you already fixed the error?
256fae49ac05d6303b5ba7b75a75a5b2169c748b yields
java.lang.IllegalStateException: Required class information is missing

	at org.jboss.jandex.Indexer.rebuildNestedType(Indexer.java:989)
	at org.jboss.jandex.Indexer.resolveTypePath(Indexer.java:842)
	at org.jboss.jandex.Indexer.resolveTypeAnnotation(Indexer.java:718)
	at org.jboss.jandex.Indexer.resolveTypeAnnotations(Indexer.java:619)
	at org.jboss.jandex.Indexer.index(Indexer.java:1678)
	at org.jboss.jandex.test.TestClassBounds.classBounds(TestClassBounds.java:15)

@n1hility ,

Gradle does not cache the results of failure tasks (it is not implemented in the current Gradle versions)
I can reproduce Required class information is missing failures locally.

For instance, I download calcite-work.tgz, I take calcite/core/build/classes/java/main/org/apache/calcite/adapter/clone/ArrayTable$1.class file (1477 bytes), and I run the following:
public class TestClassBounds {
    @Test
    public void classBounds() throws IOException {
        Indexer indexer = new Indexer();
        ClassInfo info = indexer.index(new FileInputStream("/tmp/ArrayTable$1.class"));
        System.out.println("info = " + info);
        Index index = indexer.complete();
        System.out.println("subclasses");
        index.printSubclasses();
        System.out.println("annotations");
        index.printAnnotations();
    }
}

The error can be reproduced as follows: https://github.com/wildfly/jandex/issues/92
Are you sure you already fixed the error?
256fae49ac05d6303b5ba7b75a75a5b2169c748b yields
java.lang.IllegalStateException: Required class information is missing

	at org.jboss.jandex.Indexer.rebuildNestedType(Indexer.java:989)
	at org.jboss.jandex.Indexer.resolveTypePath(Indexer.java:842)
	at org.jboss.jandex.Indexer.resolveTypeAnnotation(Indexer.java:718)
	at org.jboss.jandex.Indexer.resolveTypeAnnotations(Indexer.java:619)
	at org.jboss.jandex.Indexer.index(Indexer.java:1678)
	at org.jboss.jandex.test.TestClassBounds.classBounds(TestClassBounds.java:15)

@vlsi thanks for looking and the pointer. For some reason I still can't reproduce on my local setup (mac and linux) [both using the test and the exact class you downloaded] so this is an odd one. I'll dig further!

@vlsi thanks for looking and the pointer. For some reason I still can't reproduce on my local setup (mac and linux) [both using the test and the exact class you downloaded] so this is an odd one. I'll dig further!

Wow it even passes running as GitHub action through the jandex maven run using your exact code and class:
https://github.com/n1hility/jandex/runs/1744092156#step:4:1087
I'll try and kick of the gradle build locally and see if I can get it to fail and debug.

Wow it even passes running as GitHub action through the jandex maven run using your exact code and class:
https://github.com/n1hility/jandex/runs/1744092156#step:4:1087
I'll try and kick of the gradle build locally and see if I can get it to fail and debug.

I finally have a local scenario, looking into it.

I finally have a local scenario, looking into it.

Does that mean the error reproduces in ceratin JVMs only?

Does that mean the error reproduces in ceratin JVMs only?

@vlsi yes, so far it looks like it is a compiler bug with anonymous classes that affects some range (don't know yet) of 8 versions. it's a bit of a comedy of errors. In a few cases I had also copied the file over without properly escaping $ So ArrayTable$1.class ended up  matching ArrayTable.class, yet when i was disassembling with javap I had escaped it and didn't notice the difference. In other cases I had built with java 11 and it worked.

@vlsi yes, so far it looks like it is a compiler bug with anonymous classes that affects some range (don't know yet) of 8 versions. it's a bit of a comedy of errors. In a few cases I had also copied the file over without properly escaping $ So ArrayTable$1.class ended up  matching ArrayTable.class, yet when i was disassembling with javap I had escaped it and didn't notice the difference. In other cases I had built with java 11 and it worked.

oh yeah and then i lost my internet connection. so this bug is resisting being fixed :)

oh yeah and then i lost my internet connection. so this bug is resisting being fixed :)

@vlsi We now have a clean run! 🎉

@vlsi We now have a clean run! 🎉

@vlsi I have released 2.2.3.Final including all of these fixes.

@vlsi I have released 2.2.3.Final including all of these fixes.

@n1hility , thanks for the fast release. I'll reiterate with Calcite as the release appears on OSSRH (it is not there yet: https://repo.maven.apache.org/maven2/org/jboss/jandex/ ).
I wonder if you have the changelog somewhere.
It might be helpful to put some notes there, especially taking into account the nature of the issues was moot and the exceptions were quite puzzling.
I guess we'll need to convince @vladmihalcea to bump Hibernate's jandex dependency to prevent the users from running into issues like https://stackoverflow.com/a/65853462/1261287.

@n1hility , thanks for the fast release. I'll reiterate with Calcite as the release appears on OSSRH (it is not there yet: https://repo.maven.apache.org/maven2/org/jboss/jandex/ ).
I wonder if you have the changelog somewhere.
It might be helpful to put some notes there, especially taking into account the nature of the issues was moot and the exceptions were quite puzzling.
I guess we'll need to convince @vladmihalcea to bump Hibernate's jandex dependency to prevent the users from running into issues like https://stackoverflow.com/a/65853462/1261287.

@vlsi I'm no longer working on the Hibernate project, so you are better off talking to @Sanne about Hibernate issues.

@vlsi I'm no longer working on the Hibernate project, so you are better off talking to @Sanne about Hibernate issues.

Good idea, thanks!

https://hibernate.atlassian.net/browse/HHH-14415

Good idea, thanks!

https://hibernate.atlassian.net/browse/HHH-14415


Use socks5-proxy dialer when BOSH_ALL_PROXY has ssh+socks5:// schema

Uses the socks5-proxy dialer when BOSH_ALL_PROXY has ssh+socks5:// schema and the path to an ssh key for the jumpbox with ?private-key=.
Reference Issue: https://github.com/cloudfoundry/bosh-cli/issues/324
There was an error running dep ensure to add the socks5-proxy package. @zachgersh (the dep wizard) determined that the path to github.com/pivotal-golang/clock needed to be changed to code.cloudfoundry.org/clock in a test.
This was the error:
~/go/src/github.com/cloudfoundry/bosh-utils |master ↑1 ✓|
gl $ dep ensure
ensure Solve(): No versions of github.com/pivotal-golang/clock met constraints:
	master: Could not introduce github.com/pivotal-golang/clock@master, as its subpackage github.com/pivotal-golang/clock/fakeclock does not contain usable Go code (*pkgtree.NonCanonicalImportRoot).. (Package is required by (root).)
	master: Could not introduce github.com/pivotal-golang/clock@master, as its subpackage github.com/pivotal-golang/clock/fakeclock does not contain usable Go code (*pkgtree.NonCanonicalImportRoot).. (Package is required by (root).)
direnv: error .envrc is blocked. Run `direnv allow` to approve its content.

@genevievelesperance - changed the base of this PR to develop 👍

@zachgersh Added


Suddenly My releases disappeared when I did helm list

Output of helm version:
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.10", GitCommit:"7a578febe155a7366767abce40d8a16795a96371", GitTreeState:"clean", BuildDate:"2019-05-01T04:05:01Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AWS-KOPS
it's really weird, I upgraded my helm 4 days back from 2.16.1 to 3.0.0 .
please let me know how can i restore my previous releases
Can downgrade will help into this  ?

You need to use the --all-namespaces flag now, for deletion for example you also need to specify the release's namespace (if not using default namespace).

$ helm list --all-namespaces
NAME	NAMESPACE	REVISION	UPDATED	STATUS	CHART	APP VERSION
@Jabbo16 it is still giving me empty sir

Can you check the secrets and configmaps in all namespaces? Using kubectl get secrets,configmaps -A those are where usually releases information is stored, based on your installation. Do check it out and look for release names and versions in the secret or confimap names.
And how were these releases installed? Using Helm v2 or v3?

I did  kubectl get secrets,configmaps -A and i got as shown below
kube-system            configmap/dev-notification-dispatch.v200                                       1      2d
kube-system            configmap/dev-notification-dispatch.v201                                       1      2d
kube-system            configmap/dev-notification-dispatch.v202                                       1      2d
kube-system            configmap/dev-notification-dispatch.v203                                       1      2d
kube-system            configmap/dev-notification-dispatch.v204                                       1      2d
kube-system            configmap/dev-notification-dispatch.v205                                       1      2d
kube-system            configmap/dev-notification-dispatch.v206                                       1      2d
kube-system            configmap/dev-notification-dispatch.v207                                       1      1d
kube-system            configmap/dev-notification-dispatch.v208                                       1      1d
kube-system            configmap/dev-notification-dispatch.v209                                       1      3h
which indicates the last one happened 3 hours ago.
And how were these releases installed?
helm install repo-name --name release-name --namespace NAMESPACE --set-string timestamp=dev-random-generated-number
after that i always uses upgrade for new deployment
helm upgrade repo-name  release-name --namespace NAMESPACE --set-string timestamp=dev-random-generated-number
Using Helm v2 or v3?
If you are asking about helm version , so previous one was v2.14.3

Okay, switching from v2 to v3 needs some small effort as the release information is stored differently.
I'm assuming helm ls works for you with version 2.14.3 and even 2.16.1 ( latest v2 version ). To move to v3 you need to use the 2to3 plugin  https://github.com/helm/helm-2to3 then helm ls will work with helm version 3.0.0 :) but not with helm v2 anymore. Both are incompatible. But you can get rid of tiller in v3, for good :) ;)

@karuppiah7890
suppose I don't want to go v3.0.0 right now, it is my production setup.  I want to my previous setup back as it was working fine for me.
So what should i do ?
Thanks
If not then i will have to go v3 without any reason.

You can just keep using v2.14.3 and there should be no problems.
And the latest in v2 is 2.16.1 . You could update to v2.16.1 for some features and support for kubernetes v1.16 if you want that

Yep. Looks like nothing has changed on the backend. This system hasn't been migrated to the new storage backend for Helm 3. Continue to use it as normal, and use the helm-2to3 plugin when you're ready to migrate.
Closing as answered. Thanks!

@karuppiah7890 Thanks a lot. It got fixed. In my kube-system tiller version was v2.16.0, so same i installed helm in my deployment server by downgrading.
Thanks

I'm having the same issue, and instead, I want to migrate to v3 following the guide.
I notice in the prerequisite of the docs that:
Helm v2 client installed on a system which manages releases on one to many clusters
Helm v3 client with 2to3 plugin installed on the same system```

Both v2 and v3 clients are required, while I installed helm via homebrew. Does anyone have experience on how to get both versions at the same time?


Add validation tool jar to tarball

The alluxio-integration-tools-validation.jar needs to be added to the Alluxio tarball

Merged build finished. Test FAILed.

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

Merged build finished. Test PASSed.

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

alluxio-bot, merge this please.


Tribeca with new currencies not working

Hi Michael,
I was trying to use Tribeca on the LTC/BTC market on Gdax.
However is doesn't seems to work here is the log I get:
{"name":"tribeca:gateway:CoinbaseOE","hostname":"a8eded981008","pid":14,"level":40,"msg":"NO EXCHANGE ID PROVIDED FOR ORDER ID: 7225bf30-2948-11e7-a845-a154ee269027 null { message: 'price must be greater than zero (0)' }","time":"2017-04-24T23:47:58.794Z","v":0}
I think it's not that much missing haha.
Best,
Camille

Can you tell me how much you were trying to buy or sell for?

I did different try:
Size 3 and 0.1
Width 0.3, 0.1, 0.05
Mode Top and Ping pong
And always got the same result. Apart from that everything was working well, the price from the market and what I have in BTC and LTC in my account.

I was able to reproduce the issue and am addressing it in #102
I'll close this issue.


Api load json protocols

overview
Closes #1419
changelog

Added protocols/ module to API which parses, loads, and runs JSON protocol text
RPC Session uses execute_json instead of exec for *.json protocol files
Fix PD saving labware display names under wrong key
Changed some_var is 'a string' to some_var == 'a string' b/c ID is not always guaranteed to match

review requests

The .py protocols should continue to run with no problem
Can run .json protocols that follow the v1.0.0 JSON protocol schema
What else should be included in the tests?
Is delay implemented correctly? "wait": <number> should pause for N seconds, "wait": true should pause until user manually resumes. time.sleep and robot.pause respectively are appropriate, right? I'm not sure of the current state of pause-then-resume functionality in protocols

For follow-up tickets: what situations will mess up the ability to get through labware calibration?

Tested on Sunset and Moon Moon, single channel on the right mount works like a charm. confirming transfer, consolidate, and distribute performed as expected.
When attempting to test a single + multi channel protocol on both robots, we were unable to perform tip probe on a the left mount (single or multi). In both cases, when uploading a JSON protocol, the tip probe initial action overshoots the first (over and down) movement and the tip probe times out before it can hit the first switch.
We then uploaded the dinosaur.py protocol on Moon Moon to test left mount tip probe. Tip probe performed as expected and did not overshoot the first location.

🦄

Linking this back to RFC #1139 for reference


Neo4j Desktop queries return only after source events published

Expected Behavior (Mandatory)
The 'completed after' time shown in the Neo4j Desktop browser should closely reflect the actual amount of time from pressing 'Return' to when the message appeared.
Actual Behavior (Mandatory)
Queries say they took between 1 ms and 32 ms, however, the browser did not return this until several seconds later (only after I could see the message in the topic). The queries return almost immediately after disabling streams.source.enabled
How to Reproduce the Problem
Steps (Mandatory)

Configure (see below config)
Use a tool (such as kt) to tail the topic: kt consume -topic node_actions -offsets all=newest-1:
Run a simple statement, e.g CREATE (n:RandoLabel {name: 'foo'});
Observe that the query does not return until the Kafka message appears in the topic, and the 'completed after' time is significantly shorter than the actual time it took to return

Video:
Video demonstrating this behavior: https://streamable.com/wkuy2o
Specifications (Mandatory)
Relevant configuration:
streams.source.enabled=true
streams.sink.enabled=false

streams.source.topic.nodes.node_actions=*
streams.source.topic.relationships.relationship_actions=*
streams.source.schema.polling.interval=1000000

kafka.zookeeper.connect=localhost:2181
kafka.bootstrap.servers=localhost:9092

Versions

OS: macOS 10.15.5
Neo4j: 4.0.4 Enterprise
Neo4j-Streams: 4.0.2

This seems to have several interrelated factors at play.   When you call streams.publish, this is not a guarantee that instantaneously this message will be sent out on kafka.  Neo4j-streams uses a kafka client, which is subject to whatever defaults the client has (and any of your kafka.* settings).   When you publish a message, what you actually do is add it to a buffer to be published later.
That buffer then accumulates up to a certain size before sending, and always sends by some timeout.   Check the kafka docs for the "producer configuration settings", this is also referenced in the neo4j-streams manual.
As for how much time Neo4j Browser shows to execute a query, this issue would need to be taken up with the browser team, I'm just not sure how that's measured but I see what you're talking about.

@moxious re: being a blocker, I will need to do some further testing to see if this actually impacts the amount of time a query takes to execute, or whether it is simply (somehow) a visual delay of the Desktop browser.
The strangest thing that makes me feel like the Desktop return time and the Kafka plugin are related is that this immediately stops being visible when I disable the Kafka plugin. As soon as that is disabled, the Desktop return time matches the time it reports. But when Kafka is enabled, it just seems to wait for it to submit to Kafka to return the result in Desktop. Note that the delay between executing the query and sending to Kafka is not a problem for me, that makes a lot of sense and will perhaps need some tweaking, but the fact that it seems to hold up the return of the query.

Didn't we also have an async mode for the procedures?
The procs are synchronous by default.
Ah there was a guy who changed the async behavior :)
https://github.com/neo4j-contrib/neo4j-streams/pull/161/files
So we should re-add that.

Ah, that's an excellent point - this was changed to be synchronous on purpose.  The idea was that if it's not synchronous, you could async publish the message, and the message could fail at the kafka client layer and never go out.  In this case, it would "fail silently" and there'd be no way for the user to know it, also you couldn't chain cypher queries if it's totally async.
I mean I think probably this is blocking for the network send, and it's not like the query is taking a lot of time to return.  Question is if making it async is worth the downsides that we previously had, and worked around to get to the sync behavior.

I hadn't really gotten that far with our concept of it yet, but rolling the transaction back if a Kafka write fails would actually help out a lot (or at least the configurable option for that behavior if not the default). The question is what to do if one or more Kafka writes succeed and other(s) fail, I guess in that case we could transmit the start/rollback/commit of the transaction and ensure that a commit isn't implied in absence of one

@ivangreene can you please try with the last release?

@conker84 back in this area now and I can confirm that the behavior is now as expected, the queries return in the expected time without waiting on submission


BEM block and modifiers concat parent class

This is a best pratice too?
.Block {
  &--modifier {

  }

  &__element {

  }
}

output:
.Block {}
.Block--modifier {}
.Block__element {}

Thanks for the question!
We don't recommend that style because it hurts the findability of the selectors.


Drop older ESLint versions from peerDependencies

Companion issue to #232 – I think it makes sense to simultaneously drop support for a lot of the older ESLint versions.
We could investigate how this would impact the ecosystem that uses @eslint-community/eslint-utils / eslint-utils – which peer dependencies that those plugins have and whether they would be forced into major releases as well or whether we would simply align with what they are already using.
Considering that ESLint 8 will reach End-Of-Life in less than a month I would say that we should drop everything older than ESLint 8 and maybe even ESLint 8 itself.
If ESLint themselves are not prepared to keep ESLint 8 up to date, I'm not sure if we should go the extra mile to keep the plugin ecosystem up to date for ESLint 8?
(Maybe we could discuss this at an @eslint-community/core-team level as well?)

To get all of the dependents of @eslint-community/eslint-utils I ran this command:
npx list-dependents list --field engines @eslint-community/eslint-utils --include-historic --field peerDependencies

I piped the output of that into this command to sort it and format it to markdown:
npx list-dependents-cli filter --sort-download --field engines.node --field peerDependencies.eslint --min-downloads=1000 --pretty-print --markdown

It shows that the outlier for this issue and #232 are mainly these plugins:

vue
jsonc
svelte
json-schema-validator
css

But I think it also shows that the majority of the users have dropped ESLint versions older than 8 and Node.js versions older than 18.
If we want to be very kind maintainers we could open an issue in each of the mentioned plugins, asking if they are okay with also bumping.
Modules

Name
Dependents
Downloads
engines.node
peerDependencies.eslint

eslint
424118
162066540
^18.18.0 || ^20.9.0 || >=21.1.0
-

@typescript-eslint/utils
742
158983699
^18.18.0 || ^20.9.0 || >=21.1.0
^8.57.0 || ^9.0.0

eslint-plugin-vue
47028
11711575
^14.17.0 || >=16.0.0
^6.2.0 || ^7.0.0 || ^8.0.0 || ^9.0.0

eslint-plugin-unicorn
7871
11663513
>=18.18
>=8.56.0

eslint-plugin-n
8503
11423923
^18.18.0 || ^20.9.0 || >=21.1.0
>=8.23.0

eslint-plugin-es-x
59
6505473
^14.18.0 || >=16.0.0
>=8

eslint-plugin-regexp
526
1512731
^18 || >=20
>=8.44.0

eslint-plugin-jsonc
1360
1463434
^12.22.0 || ^14.17.0 || >=16.0.0
>=6.0.0

eslint-plugin-svelte
1150
1276737
^14.17.0 || >=16.0.0
^7.0.0 || ^8.0.0-0 || ^9.0.0-0

@intlify/unplugin-vue-i18n
87
1164381
>= 18
-

eslint-plugin-eslint-plugin
1886
833547
^18.18.0 || ^20.9.0 || >=21.1.0
>=8.23.0

eslint-plugin-astro
112
406782
^18.18.0 || ^20.9.0 || >=21.1.0
>=8.57.0

eslint-plugin-json-schema-validator
84
285335
^14.18.0 || >=16.0.0
>=6.0.0

eslint-plugin-vue-scoped-css
70
272719
^12.22 || ^14.17 || >=16
>=5.0.0

eslint-plugin-css
18
52568
^12.22.0 || ^14.17.0 || >=16.0.0
>=7.0.0

eslint-plugin-node-dependencies
55
14052
>=14.17.0
>=6.0.0

eslint-plugin-lodash-template
21
6497
>=18.0.0
>=8.0.0

eslint-plugin-address
0
1444
-
>=8.0.0

eslint-plugin-storm-software
0
1261
-
9.5.0

Intersection of versions
engines.node: ^18.18.0 || ^20.9.0 || >=21.1.0
peerDependencies.eslint: 9.5.0
Lowest included versions
engines.node: 12.22.0 (eslint-plugin-jsonc, eslint-plugin-vue-scoped-css, eslint-plugin-css)
peerDependencies.eslint: 5.0.0 (eslint-plugin-vue-scoped-css)

@ota-meshi Looks like you are a maintainer or co-maintainer of all of the five modules I mentioned as the outliers above – what's your take on bumping ESLint and/or Node versions ranges for those?

I think it's a good idea to remove old versions from supported versions to make maintenance easier.
Some of the plugins I maintain also support old ESLint versions because I haven't had a major update in a long time. When I major update them next time, I'll drop support for the old versions.

Closed by #243


Theme editor: uploaded icons are always converted to png files

Describe the bug
Currently any images uploaded in the logo area of the theme settings page are converted to be png files. Ideally we should be preserving the original file extension.
To Reproduce
Steps to reproduce the behavior:

Navigate to the theme settings page
In the Logo Settings section click the browse button
Upload a the attached gif
Click the apply button
WHen you inspect the image that got uploaded to the top left hand side of the screen you will see it's not a png file

Expected behavior
Uploaded images should preserve their original file extension
Platform:

OpenEquella Version: 2018.2, 2019.1

The conversion to PNG here was done in order to resize the image to the same dimensions as the default openEQUELLA logo, as well as to preserve transparency if it exists. Handling animation in .gifs was not part of the scope when this was implemented, and as such maintaining file type wasn't seen as a priority. Note also, the string displayed in the logo editor that reads "Use a PNG file of 230x36 pixels for best results.".


Luxon localizer should use LLL to format month instead of MMM

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/p/sandbox/friendly-margulis-n7mfrv?file=%2Fsrc%2Findex.js
Bug description
Luxon localizer use MMM to format month, this might work fine with language like English, but it doesn't work with all the languages, like Chinese
the correct way is to use LLL
Expected Behavior
No response
Actual Behavior
No response
react-big-calendar version
1.12.1
React version
18.2
Platform/Target and Browser Versions
any browser
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a react-big-calendar issue and not an implementation issue

Would you like to open a PR for this bug?

[X] I'm willing to open a PR

Correct, which is why we have the various formats props. Please see the documentation for how you may override.

hmm, even there is a workaround, it doesn't mean the default behavior should not be improved.

@rinick

@rinick Your right, and I apologize for being so hasty. Resubmit your PR, update your branch with latest from master, and I will more thoroughly review.


when pulling: Reloading None, Fatal Error! Ok

when pulling and after it starts to reload the packages the progress window in unreal says:
"Reloading None"
after this a popup appears
"Fatal Error!"
after pressing "Ok"
Unreal shuts down.
I assume that a reload is triggered on a package that does not exist.
Can there be a fix added to double check this before triggering a reload?
The problem seemed to happen were I had a uasset on disk but not showing in the project.
[2019.02.19-16.13.06:303][539]LogWindows: Error: === Critical error: ===
[2019.02.19-16.13.06:303][539]LogWindows: Error:
[2019.02.19-16.13.06:303][539]LogWindows: Error: Fatal error!
[2019.02.19-16.13.06:303][539]LogWindows: Error:
[2019.02.19-16.13.06:303][539]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x00000000
[2019.02.19-16.13.06:303][539]LogWindows: Error:
[2019.02.19-16.13.06:303][539]LogWindows: Error: [Callstack] 0x0000000000000000 UnknownFunction []
[2019.02.19-16.13.06:303][539]LogWindows: Error: [Callstack] 0x00007ffb9fe207b1 UE4Editor-CoreUObject.dll!UnknownFunction []
[2019.02.19-16.13.06:303][539]LogWindows: Error: [Callstack] 0x00007ffb9b840e28 UE4Editor-UnrealEd.dll!UnknownFunction []
[2019.02.19-16.13.06:303][539]LogWindows: Error: [Callstack] 0x00007ffb9b83fb8e UE4Editor-UnrealEd.dll!UnknownFunction []
[2019.02.19-16.13.06:303][539]LogWindows: Error: [Callstack] 0x00007ffb8a586aa0 UE4Editor-GitSourceControl.dll!UnknownFunction []
....
[2019.02.19-16.13.06:303][539]LogWindows: Error: [Callstack] 0x00007ffbf1ad81f4 KERNEL32.DLL!UnknownFunction []
[2019.02.19-16.13.06:303][539]LogWindows: Error: [Callstack] 0x00007ffbf228a251 ntdll.dll!UnknownFunction []
[2019.02.19-16.13.06:303][539]LogWindows: Error:
[2019.02.19-16.13.06:314][539]LogExit: Executing StaticShutdownAfterError
[2019.02.19-16.13.06:323][539]LogWindows: FPlatformMisc::RequestExit(1)
[2019.02.19-16.13.06:327][539]Log file closed, 02/19/19 16:13:06

I had the same issue and ended up tracking it down to UE trying to reload a "name pointer package". When you rename an asset in UE it keeps the original file as a pointer to the new one, trying to reload that package is what makes it crash. The way to fix the issue is to go in the content browser and right click on the top level directory and then and then click "Fix up redirectors in folder". This will remove the leftover files. After that you might want to commit the changes and pull shouldn't crash anymore.

That's actually a really good news ; I was never able to reproduce it.
There might even be a more robust solution; you should post this as a bug report to Epic Games because it's most likely a thing to fix int the Engine

Agreed, it is on my TODO list to open a bug with Epic.

Here is the public issue that Epic opened to track the problem https://issues.unrealengine.com/issue/UE-63030

Thanks a lot, that's great


GDAX Socket Timeout Exception

From time to time, I'd get SocketTimeoutException on GDAX.
java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
	at java.net.SocketInputStream.read(SocketInputStream.java:170)
	at java.net.SocketInputStream.read(SocketInputStream.java:141)
	at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
	at sun.security.ssl.InputRecord.read(InputRecord.java:503)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
	at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930)
	at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
	at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
	at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
	at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704)
	at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
	at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
	at si.mazi.rescu.HttpTemplate.receive(HttpTemplate.java:122)
	at si.mazi.rescu.RestInvocationHandler.receiveAndMap(RestInvocationHandler.java:156)
	at si.mazi.rescu.RestInvocationHandler.invoke(RestInvocationHandler.java:120)
	at com.sun.proxy.$Proxy11.getProductOrderBook(Unknown Source)
	at org.knowm.xchange.gdax.service.GDAXMarketDataServiceRaw.getCoinbaseExProductOrderBook(GDAXMarketDataServiceRaw.java:56)
	at org.knowm.xchange.gdax.service.GDAXMarketDataService.getOrderBook(GDAXMarketDataService.java:50)

You could try increasing the timeout that rescu uses. See https://github.com/mmazi/rescu

Kindly point out how specifically we can set on this library? The example BitstampTradeServiceRaw  on rescu doesn't give examples like
rescu.http.readTimeoutMillis = 5000             # Read timeout in milliseconds when performing HTTP requests. The default is 30000 (30 seconds).
rescu.http.readProxyHost = www.example.com      # HTTP proxy host. Both host and port must be set in order to use a proxy.
rescu.http.readProxyPort = 80                   # HTTP proxy port. Both host and port must be set in order to use a proxy.
rescu.http.ignoreErrorCodes = true              # If set to true, the HTTP response body never be parsed as Exception but always as the method response type. Defaults to false.

Sure thing....
"Rescu can be configured by adding a rescu.properties file in your classpath."


Explicitly send api_version with every request

Default api_version to 1 unless another one is specified.  This is required because clio defaults to using v2 which isn't a formalized spec yet.

Clio defaults to v1 now instead of v2.


Update LDAP documentation

Pretty straightforward request, but I noticed this is not called out in the documentation:
Currently, the LDAP.md file contains the following section:
AUTH_LDAP_USER_ATTR_MAP = {
    "first_name": "givenName",
    "last_name": "sn",
}

I tried adding "email_address": "mail" as an additional dict value, but I needed to use the key name email instead of email_address.
In summary, the page for LDAP documentation should be updated to reflect the following:
AUTH_LDAP_USER_ATTR_MAP = {
    "first_name": "givenName",
    "last_name": "sn",
    "email": "mail"
}

Looks good, could you put in a PR for this please?

Done.  Pull #1386
FYI - I also noticed that the links  on netbox.readthedocs.io to both "View" and "Edit" the page (bottom left corner under the heading "On GitHub") the page doesn't work properly.  Wasn't sure the exact problem, but manually found the .md file.

Thanks!


signalbackup-tools: 20230907 -> 20230914-1

Description of changes
Update to latest version. No changes that effect build.
Diff: https://github.com/bepaald/signalbackup-tools/compare/20230907...20230914-1
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 255146 run on x86_64-darwin 1

1 package built:

signalbackup-tools

Result of nixpkgs-review pr 255146 run on aarch64-darwin 1

1 package built:

signalbackup-tools


Feature Request: Snappy Decompression

Is your feature request related to a problem? Please describe.
I encountered some blobs compressed with the Snappy algorithm in some binary file.
There isn't currently a module in CyberChef that can decompress those.
Describe the solution you'd like
A new module for Snappy decompression.
This module shouldn't need parameters to operate. Just an input bytes stream.
Compression could be nice for completeness but I have no specific use for it. I also assume it's harder to implement.
Additional context
Snappy is an encryption algorithm created by Google.
Offical info, and C++ implementation, is available here:
https://github.com/google/snappy
3rd part implementations are listed here:
http://google.github.io/snappy/
There seem to be some variations of snappy: "framing" and "hadoop".
I think the "framing" one probably contains a magic.
The variation I'm particular interested does not start with a magic, it's the "original"(?) one that starts with a VarInt representing the size of the decompressed file.
Thank you.

Sorry, this should probably be marked as "Operation"


the localStorage not working

Hi, I found the localStorage data missing after I close and reopen the application.

I assume, you passed empty string to dir(The second argument of lorca.New).
If lorca.New receive empty dir, temporary user directory is created and will be deleted when application is closed. So all user configurations will be lost including localStorage.
To avoid this, provide dir explicitly.
ui, _ := lorca.New("", "path/to/dir", 480, 320)


Terminal find highlights aren't correct

See how only pp is highlighted for the search term app

Verified on a couple of examples with gpu acceleration off.


Add translation/language-switch button/widget

Use direct link/switch:
https://translate.google.com/translate?u=https://example.org/specific-url

Set "Source Language" (sl=) and "Target Language" (tl=)
https://translate.google.com/translate?sl=   en   &tl=   nl   &u=https://example.org/en/english-specific-url

See: https://github.com/rodekruis/helpful-information/issues/601#issuecomment-1461790421
To Do

[ ] Add "sheet language" to ReferalPage-sheet, i.e: en

[ ] Set html[lang]-attribute to use it

[ ] Add "translation presets" to ReferralPage-sheet, i.e: nl=Nederlands, es=Español, ar=Arabic
[ ] Add switch-links in Header/Footer

[ ] ? Icon + drop-down in header?
[ ] ? List with text at bottom-of-page
"Translate with Google Translate in: Nederlands, Español, Arabic"

Possible solution: Switcher/dropdown in Top-bar

Use a pre-defined set of target-languages?

Needs lang/locale + labels

Possible solution: Switch-links in Footer/bottom-of-all-pages

Could be 1 or many links
Possible to show/highlight currently-used language?

See: https://www.flagsarenotlanguages.com/blog/best-practice-for-presenting-languages/

Update Elwin/Jonath: working session planned for Elwin/Anca on Monday 4 Dec. Can be finalized by the end of that day.

See https://github.com/rodekruis/helpful-information/blob/main/CHANGELOG.md#2024-06-03-v2406


BN error

hi
when I want to generate  c files I get this error "the checkpoint file contains 1-dimensional weights for conv1.bn.weight with dimensions (24,). Ensure the BatchNorm layers have been folded."
what is the problem and what is the solution?

Hello,
The hardware does not support BatchNorm (BN) layer so if you want to use a BN layer in your model, you have to fuse these layers to the preceding convolution layers (see here). If you enable Quantization Aware Training (QAT) during your model training, the code automatically folds the the batchnorm layers. So if you use qat_checkpoint.pth.tar or qat_best.path.tar, you will not get such an error during the code synthesis. If you want to use post training quantization without QAT, you may run batchnormfuser.py to fold the BN layers to the convolutional layers.

Hi
Thanks for reply
Yes,I have trained in both ways and I just have problem in none qat
So for your second choice in command how do I run my model in training
with  batchnormfuser.py
Could you please tell me in details🙏🙏
On Thu, 25 Jul 2024, 12:35 Erman Okman, @.***> wrote:

Hello,
The hardware does not support BatchNorm (BN) layer so if you want to use a
BN layer in your model, you have to fuse these layers to the preceding
convolution layers (see here
https://github.com/analogdevicesinc/ai8x-training?tab=readme-ov-file#batch-normalization).
If you enable Quantization Aware Training (QAT) during your model training,
the code automatically folds the the batchnorm layers. So if you use
qat_checkpoint.pth.tar or qat_best.path.tar, you will not get such an
error during the code synthesis. If you want to use post training
quantization without QAT, you may run batchnormfuser.py to fold the BN
layers to the convolutional layers.
—
Reply to this email directly, view it on GitHub
https://github.com/analogdevicesinc/ai8x-synthesis/issues/350#issuecomment-2249838414,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWLZTJMP5HZEYDLOCBTZ2VTZOC5TZAVCNFSM6AAAAABLMOLD62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBZHAZTQNBRGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

It is a python script that you can run from the command line. The details of the batchnormfuser is here. But we always suggest to use QAT as the direct quantization of a floating model may cause huge accuracy drop.

Thanks a lot
I have another problem in command
In the documentation is suggested to use --energy for energy during
processing but in my max78000fthr board it doesn't show
How can I get energy ?
On Thu, 25 Jul 2024, 13:46 Erman Okman, @.***> wrote:

It is a python script that you can run from the command line. The details
of the batchnormfuser is here
https://github.com/analogdevicesinc/ai8x-training?tab=readme-ov-file#command-line-arguments-1.
But we always suggest to use QAT as the direct quantization of a floating
model may cause huge accuracy drop.
—
Reply to this email directly, view it on GitHub
https://github.com/analogdevicesinc/ai8x-synthesis/issues/350#issuecomment-2249979424,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWLZTJJ4F5JSUTFC4S7KJWTZODGALAVCNFSM6AAAAABLMOLD62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBZHE3TSNBSGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

You need a (MAX78000 EvKit)[https://www.analog.com/en/resources/evaluation-hardware-and-software/evaluation-boards-kits/max78000evkit.html] to measure and observe the energy consumption. The feather board does not have an energy measurement circuitry.

thanks for reply
is there any way to calculate energy consumption and power?

There is no other straightforward approach to measure the energy consumption.


Not work with Path Intellisense in template tag

I wish to use path completion when I was typing<img<EMAIL_ADDRESS>In the past, I used to use Vetur + Path Intellisense, and they works well like this:

but Volar + Path Intellisense doesn't works in template tag, by th way, it's ok in script tag.
setting.json like this:
 "path-intellisense.mappings": {
    "@": "${workspaceRoot}/src/"
  },

jsconfig.json like this:
{
  "strict":true,
  "compilerOptions": {
    "baseUrl": "./",
    "paths": {
        "@/*": ["src/*"]
    }
  },
  "exclude": ["node_modules", "dist"]
}

By the way, I found that after I typed <img src="@/assets/  , the path completion  worked, I don't know if this is going to help.

can you try adding a custom path in tsconfig ?
"paths":{
  "@/": ["your_path"]
}

I tried this, and it also does't work. This is my jsconfig.json
{
  "strict":true,
  "compilerOptions": {
    "baseUrl": "./",
    "paths": {
        "@/*": ["src/*"]
    }
  },
  "exclude": ["node_modules", "dist"]
}

thx~

@davidlin88 this is expected TS behavior in <script> block so no plan to change it.


GitHub bandwidth quota impacts

Just wanted to share a courtesy experience. I don't really think there is much you can do to solve this.
Using sphinx_lfs_content worked great but it (combined with fact that we rebuild docs on each commit to a PR) caused our GitHub bandwidth quota to soar.
So, we needed to disable it. We will revisit this issue in future if we have time.

I have experienced the same thing. LFS bandwidth quota on GitHub are rather restrictive and exceptionally fatal once exceeded (repository cannot be cloned anymore). As you said, there is nothing this project can do about that, it is still a valid workaround for projects hosted elsewhere (e.g. private GitLab instance).


more sensible API and support for https-cross-posting

Listening
const hubbie = new Hubbie({ }); // for use as a client
const hubbie = new Hubbie({ port: 8000 });
const hubbie = new Hubbie({ server: http.createServer(options) | https.createServer(options) });
const hubbie = new Hubbie({ tls: 'michielbdejong.com' }); // will try to listen on ports 80 and 443
const hubbie = new Hubbie({ peerName: 'alice' }); // for receiving messages within the same process

Peer management
hubbie.on('peer', ({ // triggered when new peer connects to you, see below
  peerName: 'bob',
  peerSecret: 'boo'
}) => true/false); // return false if the secret looks wrong
hubbie.addPeer({ // returns immediately, see below
  peerName: 'alice',
  myName: 'bob',
  mySecret: 'boo',
  peerUrl: 'ws://localhost:8000' | 'wss://michielbdejong.com' | undefined | 'http://localhost:8000' | 'https://michielbdejong.com' // see below for explanation of peerUrl
});
hubbie.removePeer(peerName);
hubbie.listPeers() => [ { peerName, peerType: 'ws-server' | 'http-peer' | 'in-mem' | 'ws-client', peerUrl } ]

Messaging
There is no request/response mechanism, all messages are one-way. Messages will be queued indefinitely until they can be sent once.
hubbie.send(peerName, message); returns promise (rejects if peerName unknown but will not time out)
hubbie.on('message', (peerName, message) => { });

Once connected

When Alice calls hubbie.send('bob', 'asdf'), Alice will see a 'message' event { peerName: 'alice', message: 'asdf' }
When Bob calls hubbie.send('alice', 'asdf'), Alice will see a 'message' event { peerName: 'bob', message: 'asdf' }

Different ways for peers to connect
Client-Server using WebSockets
There are several ways to start a server; on a port, passing it a http server, or giving it a domain name for tls with on-the-fly LetsEncrypt registration.

Alice starts a server using hubbie = new Hubbie({ port | server | tls }).
Bob instantiates hubbie = new Hubbie({}), and connects to Alice using hubbie.addPeer({ peerName: 'alice', myName: 'bob', mySecret: 'boo', peerUrl: 'ws://localhost:8000' | 'wss://michielbdejong.com' });.
Alice sees a 'peer' event { peerName: 'bob', peerSecret: 'boo' }, recognizes Bob's secret 'boo', and returns true, after which Alice and Bob are connected.

The peerUrl should be a WebSocket URL.
Server-Server using http cross post

Alice starts a server using a 'port' or 'tls' option in the Hubbie constructor. If you give a 'server' option, it will only listen for WebSockets, not for http cross post.
Bob also starts a server using a 'listen' or 'tls' option.
Alice configures her connection to Bob using hubbie.addPeer({ peerName: 'bob', myName: 'alice', mySecret: 'pssst', peerUrl: 'http://localhost:8001' | 'https://bob.com' });
Bob configures his connection to Alice using hubbie.addPeer({ peerName: 'alice', myName: 'bob', mySecret: 'boo', peerUrl: 'http://localhost:8002' | 'https://alice.com' });
The first time Bob sends a message, Alice will first see a 'peer' event { peerName: 'bob', peerSecret: 'boo' }, recognizes Bob's secret 'boo', and returns true, after which Alice will get the 'message' event for that messages. Subsequent messages from Bob will go straight through. And likewise for messages from Alice to Bob.

In-memory
Listen for messages from other hubbies that live within the same process. No need for secrets here:
const alice = new Hubbie({ myName: 'alice' });
const bob = new Hubbie({ myName: 'bob' });
alice.send('bob', 'hello!');
bob.on('message', (peerName, message) => {
  bob.send(peerName, 'hello to you too');
});

way to get there incrementally:

[ ] implement firing peer event
[ ] check peer event response before adding peer
[ ] implement firing message event
[ ] move listen config setting out of constructor
[ ] ...

The message queue for a peer should be independent of their channel object. it could even be that a peer disconnects their websocket and then later connects through webrtc or whatever, with the same correct name and secret, and the connection should continue.
So maybe we need:

listeners for onPeer
listeners for onMessage
a send-method and queues with timers that will check if a channel exists, with exponential backoff
servers
clientConnectors
channels, which can be ws objects from a server, or ws objects from a clientConnector

for in-memory, each Hubbie has its own name, and message queues for other names. when a queue tries to send, it can call the singleton with (from, to, msg)
for server-side, queues can call the server with (to, msg)
for client-side, queues can call the client with (msg)

to simplify this, each hubbie can keep a hash of queues and a hash of channels.
when a client connects, or someone connects to a server, the ws object is added as a channel.
when a Hubbie listens for myName:

it creates its own channels for all existting hubbies
it introduces itself to all existing hubbies so they can create channels back
it adds itself to the singleton list of hubbies

addClient instead of addPeer.


Syntax highlighting broken?

11.0.10

11.0.9

The grammar and highlighting is provided by https://github.com/Microsoft/TypeScript-TmLanguage. And yes, we updated it recently in https://github.com/TypeStrong/atom-typescript/pull/1358.
I don't think it's broken, it just added support.class.component scope for component-tags, which I find is a reasonable change.

Oh I see! That's reasonable.


Release/v0.25.0

@mluypaert I don't get it.  I've done the merge back from production but still getting conflicts on RELEASE-NOTES.md.  I can't resolve them via the command line as Github suggests because we can't push changes to release branches.

! [remote rejected]   release/v0.25.0 -> release/v0.25.0 (protected branch hook declined)

! [remote rejected] release/v0.25.0 -> release/v0.25.0 (protected branch hook declined)

@oblodgett Did you re-enable release branch protection rules? I though I deleted those earlier already 🤔
@markquintontulloch Try again now, I've deleted the branch protection rule on the release branches that was blocking this.


Steven issue 110

Fixed NavBar.jsx and App.jsx files. Both had constants that were converted to functions and this change was reverted.

LGTM


catch all notice changes

This notice was skipping over these changes due to the extra <E> tags.

:+1:


DCOS_OSS-981: Host port auto-assign issue

This is the master fix of #2186 Host port auto-assign issue
Detailed explanation: https://jira.mesosphere.com/browse/DCOS_OSS-981
One more issue I fixed accidentally along with it: https://jira.mesosphere.com/browse/DCOS_OSS-1107 😆
Turned out we were wrong assuming that ports auto assign works per endpoint, in fact it works on the app level. This PR moves the checkbox from the endpoint form to the network form and changes the way this checkbox affects port field in a portDefinition. When auto assign is checked JSONReducer replaces any value for all the ports with 0, when the checkbox is not checked it emits previous value or 0.
We might want to create a custom validator that will force a user to enter a port in case the auto assign feature is off.
Testing:
Apart from the form interaction. Launch an 1 instance app with auto-assigned ports. Wait until it is running. Edit the app with the form bump instances to an arbitrary number, say 6. Save. Verify that all the instances are running, not Waiting.
Visual:

retest this please

Should we reset the hostPort in the form when toggling assign ports automatically? The old auto-assigned port value is kept. There is inconsistency between the JSON and the form.

@MatApple good catch!
Though this is not how I'd assume <FieldInput value={null} /> to work. I had to set the value to an empty string to clear the field. In my understanding null is a value, wheres undefined is not so I'd expect providing null to the <FieldInput /> clears it's value.

Not a blocker but it would be nice to show an error when auto assign is selected and a port other then 0 is defined instead of replacing the value. What do you think?

@orlandohohmeier I think that edge cases like that is the another level of UX already. Because now JSON has contradicting values: requirePorts: false and a port: 9999 so possible solutions is to: 1. Say "Hey, fix your JSON" and block everything
2. Uncheck Ports auto-assign
3. Reset the port value
How do we exactly know whats right?
I'm growing in concern that having the split edit view is a good idea. If a user wants/needs to edit JSON the Form should disappear at this point. It should be either Form or JSON editor, not both together @leemunroe

Reiterating that port auto assign does not deserve its own heading and section as it is closely related to "Service Endpoints". Is moving this being tracked separately (per this JIRA)?

nvm found it :)
https://github.com/dcos/dcos-ui/pull/2216


Is it possible to remap "Evaluate Motion"?

I'm trying to remap "evaluate motion" to "E", while leaving all the other keybindings behind local leader as they are. I found all sorts of :ConjureEval* commands in the command input, but I didn't see :ConjureEvalMotion. Is it possible to rebind it from lua?
Sorry if this is a noob question, I'm fairly new to neovim.

Yep, you can! It looks kind of awkward and it's documented somewhere in :h conjure but this should do the trick:
let g:conjure#mapping#eval_motion = ["E"]

So you wrap the mapping string in a list to signify that it's kind of a raw, unprefixed, mapping. As you can tell, this was added quite late after I committed to the simple auto prefixed string. Kinda gross API really but it does the job until I one day rewrite all of the mapping code once again 😅

Thanks! And thanks for this awesome plugin!


I recently reformatted onto a SSD and I didn't have this problem previously.

Out of curiosity, do you have a chrome tab with a 'poe build' open in the background?
I get the same issues when a chrome tab is open with a build in it - fps on alt tabbing etc starts spiking up and down from 20/40 to 200 fps.

I've experienced this issue as well, and I think it has to do with the overlay being tied (somehow) to a different max FPS. (Maybe Windows' FPS?)
I actually fixed it by moving all the overlay elements (menu, trade request list, etc) off the game window and onto my second monitor. Doing so instantly popped my FPS back up from 60 to 140ish.

I unfortunately do not use a second monitor, but I did notice the issue also happens when a steam friend comes online, which seems to indicate any overlay fucks it up. idk


[#20][SRM-30] Add markets page

#20
SRM-30

Just an initial commit with the new jsp file. More commits on the way.


#to_s doesn't round-trip for some values

Unit(1, 2, "m") # => Unit("1/2 m")
Unit("1/2 m") # => Unit("1/2 m^-1")

I ran into this problem after doing some arithmetic operations on units. For example:
a = Unit('5 cm')
b = Unit('1 cm')
c = a - b # => Unit("4/1 cm")
c.to_s # => "4/1 cm"
Unit(c.to_s) # => Unit("4 cm^-1")

It makes sense that "4/1 cm" needs to be parsed as "4 / (1 cm)", for correct operator precedence. The problem to me is that #to_s isn't outputting a string that can be properly parsed. If it included the necessary parentheses, that would solve it. E.g., "(4/1) cm". (In this particular case, reducing the fraction would be even better...)

PR #26 solves the issues I was having, and should solve @pivotale20's issue, too.
a = Unit('5 cm')
b = Unit('1 cm')
c = a - b # => Unit("4 cm")
c.to_s # => "4 cm"
Unit(c.to_s) # => Unit("4 cm")

and
Unit(1, 2, "m") # => Unit("(1/2) m")
Unit("(1/2) m") # => Unit("(1/2) m")

More generally, this should hold:
Unit(unit.to_s) == unit


Failed to activate the tree-view-auto-reveal package

[Enter steps to reproduce:]

Rebooted atom after receiving a package update.

Atom: 1.30.0 x64
Electron: 2.0.5
OS: Mac OS X 10.13.6
Thrown From: tree-view-auto-reveal package 1.1.3
Stack Trace
Failed to activate the tree-view-auto-reveal package
At Cannot read property 'isVisible' of undefined

TypeError: Cannot read property 'isVisible' of undefined
    at Object.activate (/packages/tree-view-auto-reveal/lib/tree-view-auto-reveal.js:16:25)
    at Package.activateNow (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/package.js:230:33)
    at measure (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/package.js:206:33)
    at Package.measure (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/package.js:88:25)
    at activationPromise.Promise (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/package.js:200:20)
    at new Promise (<anonymous>)
    at Package.activate (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/package.js:198:38)
    at PackageManager.activatePackage (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/package-manager.js:695:42)
    at config.transactAsync (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/package-manager.js:670:36)
    at Config.transactAsync (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/config.js:866:28)
    at PackageManager.activatePackages (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/package-manager.js:668:23)
    at PackageManager.activate (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/package-manager.js:647:50)
    at loadStatePromise.loadState.then (/Applications/AtomLite/Atom.app/Contents/Resources/app/src/atom-environment.js:875:27)
    at <anonymous>

Commands

Non-Core Packages
atom-better-tabname 1.6.0
atom-clock 0.1.16
atom-fuzzy-grep 0.17.2
atom-ide-ui 0.13.0
atom-sublime-monokai-syntax 0.4.4
atom-unsaved-changes 0.4.0
auto-detect-indentation 1.3.0
autocomplete-modules 2.2.0
busy-signal 1.4.3
close-on-left 0.9.2
custom-title 1.0.1
Dependents 1.6.6
docblockr 0.13.7
fb-phabricator 0.0.0
git-blame 1.7.0
git-plus 8.1.0
hey-pane 1.1.0
highlight-selected 0.14.0
hyperclick 0.0.0
ide-flowtype 0.23.1
intentions 1.1.5
javascript-refactor 0.7.1
js-hyperclick 1.13.3
js-refactor 0.8.1
line-diff-details-plus 1.9.1
linter 2.2.0
linter-eslint 8.4.1
linter-flow 5.6.1
linter-ui-default 1.7.1
minimap 4.29.9
minimap-bookmarks 0.4.2
minimap-cursorline 0.2.0
minimap-find-and-replace 4.5.2
minimap-git-diff 4.3.1
minimap-highlight-selected 4.6.1
multiline-tab 0.2.1
open-git-modified-files 0.2.4
open-on-phabricator 1.3.1
prettier-atom 0.55.2
quick-file-actions 0.2.2
refactor 0.11.5
tidy-tabs 0.4.0
todo-show 2.3.2
tree-view-auto-reveal 1.1.3

The same issue happens every time when a new project is opened, no matter either from a CLI or by using Atom File-Open menu.
The error was thrown from the tree-view-auto-reveal package. This issue has already been reported.

Atom version: 1.35.1

Thanks @johnschult for your fix. I've added your commit.


Accommodate ORB product

Implements a hidden option: mode = orb (https://github.com/SAR-ARD/S1_NRB/commit/45056e9882a4f4da0185f32e362882c5241123ca)

Can be chosen instead of ard. Currently, this option has only an effect on command-line messages, file- and directory naming as well as some metadata entries. Processing steps are not changed.

Renaming as discussed in #114:

NRB_PATTERN -> ARD_PATTERN (https://github.com/SAR-ARD/S1_NRB/commit/1703bca7e8c7bda183c82b193513de76ac48e4d3)
ORB_MAP -> OSV_MAP (https://github.com/SAR-ARD/S1_NRB/commit/dea8327fd72b770f3dab9016506ef1e5197f8d7c)
nrb_dir -> ard_dir (https://github.com/SAR-ARD/S1_NRB/commit/8c7b9cad46ddcfc626085c1f66aba4dbb45558f1)
rtc_dir -> sar_dir (https://github.com/SAR-ARD/S1_NRB/commit/de0cd1d76c64dc25d29a2392cd4dbbc52a29ac8a)
mode: rtc + nrb -> sar + ard (https://github.com/SAR-ARD/S1_NRB/commit/132bbfa1222d8ea1a9cc1fde9f6df2524cfe6f75)

Update references to NRB and RTC to ARD and SAR where appropriate (e.g., docstrings and variable names) (https://github.com/SAR-ARD/S1_NRB/commit/c4fb7fb320fad289d8c761b0c419b09bb924aed1)
XML: flexible namespace generation, i.e. automatically choose s1-nrb or s1-orb namespace (https://github.com/SAR-ARD/S1_NRB/commit/a9c07d19116c869ca02d465f0bcecc58f8c0c0ee)
Update Documentation (https://github.com/SAR-ARD/S1_NRB/commit/8c4a901a297355cb28b8e133b8a8b677d2dcfe52)
Update metadata.stac.make_catalog (https://github.com/SAR-ARD/S1_NRB/commit/9664cda8f741565b2128b32a558e10abd8aeaef4)

closes #114

What is your opinion on merging #122 and this one soon, @johntruckenbrodt ?


HBASE-23337 Release scripts should rely on maven for deploy.

- switch to nexus-staging-maven-plugin for asf-release
- refactor release-build to use mvn deploy and its output.
- cleaned up some tabs in the root pom

first commit corresponds to a rebase of v1 from jira.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 55s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
shelldocs
0m  0s
Shelldocs was not available.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+1 :green_heart:
mvninstall
5m 26s
master passed

+1 :green_heart:
compile
2m 58s
master passed

+1 :green_heart:
shadedjars
4m 39s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 49s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 51s
the patch passed

+1 :green_heart:
compile
2m 55s
the patch passed

+1 :green_heart:
javac
2m 55s
the patch passed

-1 :x:
shellcheck
0m  2s
The patch generated 1 new + 30 unchanged - 32 fixed = 31 total (was 62)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedjars
4m 36s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
15m 28s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
javadoc
2m 50s
the patch passed

_ Other Tests _

-1 :x:
unit
216m 44s
root in the patch failed.

+1 :green_heart:
asflicense
0m 48s
The patch does not generate ASF License warnings.

272m 12s

Reason
Tests

Failed junit tests
hadoop.hbase.snapshot.TestExportSnapshotNoCluster

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-887/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/887

Optional Tests
dupname asflicense shellcheck shelldocs javac javadoc unit shadedjars hadoopcheck xml compile

uname
Linux 8674e91ba6ce 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-887/out/precommit/personality/provided.sh

git revision
master / d6539350ed

Default Java
1.8.0_181

shellcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-887/1/artifact/out/diff-patch-shellcheck.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-887/1/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-887/1/testReport/

Max. process+thread count
5519 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-887/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) shellcheck=0.7.0

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 33s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
shelldocs
0m  0s
Shelldocs was not available.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+1 :green_heart:
mvninstall
5m 28s
master passed

+1 :green_heart:
compile
2m 59s
master passed

+1 :green_heart:
shadedjars
4m 37s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 56s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 11s
the patch passed

+1 :green_heart:
compile
2m 58s
the patch passed

+1 :green_heart:
javac
2m 58s
the patch passed

+1 :green_heart:
shellcheck
0m  1s
The patch generated 0 new + 30 unchanged - 32 fixed = 30 total (was 62)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedjars
4m 39s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
16m 13s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
javadoc
2m 56s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
272m  0s
root in the patch passed.

+1 :green_heart:
asflicense
0m 45s
The patch does not generate ASF License warnings.

327m 38s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-887/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/887

Optional Tests
dupname asflicense shellcheck shelldocs javac javadoc unit shadedjars hadoopcheck xml compile

uname
Linux c59190c6f171 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-887/out/precommit/personality/provided.sh

git revision
master / d6539350ed

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-887/2/testReport/

Max. process+thread count
5651 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-887/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) shellcheck=0.7.0

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Yeah there is one already


Crash on Companion 3.2.2 (3.2.2+6688-stable-7417d2a0)

Hi
It crash every time I try on companion 3.2.2+6688-stable-7417d2a0.
Here is the log : Instance/ModuleHost: Unhandled error restarting connection: Error: Restart forced
I would like to stay on this version of companion cause i use the deprecated OSC API. I'm not able to use the new one with a soft that i use ... .
Any idee to what to do ?
Thank's
Martin

What connections are you using?  There are no plans to release subsequent stable versions of 3.2.x

Thank you for your respond, and pardon my poor english.
I'm not shure to get you.
This module will never work with that version of companion ? Will it work with the last version of companion ?
I need to connect UE150 but the native module is not as complete as yours.
Thank's again

You can try a newer version of Companion, but panasonic-ptz module has been on v2.4.0 since January.  I'm going to move this issue to that module.


RADIUS MAC authentication on Captive Portal

Actually (version 16.7.9)  the mac address of the user isn't send with the authentication to the radius server.
Could you please add this feature for the next releases?
Thanks!

Just to verify: I assume this Issue was closed as it won't be added (and not because it was already implemented), right?
So no MAC-based Auth of the Captive Portal for opnsense?

timed out, nobody working on it.


Link profile page with navigation and side bar

As a user I want to use the navigation or side bar to switch to my profile page, so that I can easily access my profile.
Dependencies

#28
#29
#42
#23

Acceptance Criteria

[ ] profile icon is in navigation and side bar
[ ] if I click on the icon I will be redirected to my profile page

Sidebar:

Navigation Bar in Home Screen:

We're blocked on https://github.com/hpi-swt2/bookkeeper-portal-red/issues/28 and https://github.com/hpi-swt2/bookkeeper-portal-red/issues/29. It looks like there's a branch where progress is being made. Once that's merged, we should be able to fulfil this issue by placing the link here:
https://github.com/hpi-swt2/bookkeeper-portal-red/blob/210d550f91f4c6769f322fb8f8f39067e7b91ddc/app/views/layouts/application.html.erb#L66
-
+ <a href="<%= profiles_me_path %>" class="text-white">

This issue was already solved by #29.


kubernetes depends on requests, force requests to use chardet to avoid log spam

Merging as this was a regression caused by https://github.com/appgate/sdp-operator/pull/127


Extension Untrusted

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

VS Code Version: 1.75
OS Version: RHEL 7

Steps to Reproduce:

Behind the corporate firewall, install any extension manually, i.e., using .vsix file.
The vsix file is downloaded from official Visual Studio Marketplace.
Here I am trying to install Python and Pylance extension.
We are installing the extension on the remote server using Remote-SSH
The error throwing is Untrusted, Untrusted, Untrusted.

I am currently using latest VS code only!

https://github.com/microsoft/vscode/issues/173327


Move from yarn classic to a better package manager

📚 Context
We are still using yarn classic.
There are better alternatives nowadays.
Either latest npm, pnpm, or yarn modern.
They are all faster and provide a better user experience.
✔ Solution
Choose between the three mentioned and migrate away from yarn classic.
Maybe test more than one, and evaluate what works best.
I had a good experience with pnpm.
📈 Subtasks

[x] #370
[ ] evaluate yarn modern
[ ] evaluate latest npm
[ ] migrate away from yarn classic

🎯 Definition of Done

[x] new and faster package resolution mechanism

Migrated to pnpm without evaluating others. It's good enough.


Add Support for Parameter Suffixes

Adds support for parameters with static suffixes. For example, /{foo}.png.
The implementation is currently limited in that parameters with and without suffixes are considered overlapping. For example, /{foo}.png and  /{foo} cannot coexist. This restriction may be lifted in the future with a smarter implementation.
Additionally, the restriction of a single parameter per route segment still remains. This means /{foo}.{bar} is not supported. Arbitrary parameters without a / anchor can become quite complicated in terms of backtracking (similar to https://github.com/ibraheemdev/matchit/issues/41#issuecomment-1732178823), so multiple parameters are unlikely to be supported.
Resolves https://github.com/ibraheemdev/matchit/issues/17.

Yeah that seems reasonable, I think we can support it.

I updated the implementation to support overlapping suffixes, e.g. /foo, /{foo}.jpg, and /{foo}.png are not conflicting. This does impose a small performance regression by introducing an extra node after any route parameter, even without a suffix. It may be possible to special case the parameters without a suffix (just /) to avoid this in the common case.


Update rm command

Proposed changes
This PR update rm command. It adds status check and supports stdout flush.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[X] I have signed the CLA
[X] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
N/A

Coverage remained the same at 100.0% when pulling 1cddedb0a999b04b2781107da0042304006cabd2 on fisuda:update/rm_cmd into 5736d6672bf00a7935545a97489125c6308bc16f on lets-fiware:main.