Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

angular-cli: 1.0.0-beta.28.3
node: 6.10.0
os: darwin x64
Repro steps.

ng build
The log given by the failure.

As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release,
which will only support Node 6.9 and greater. This package will be officially deprecated
shortly after.
To disable this warning use "ng set --global warnings.packageDeprecation=false".
Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".
Error: Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".
at Object. (.../node_modules/@ngtools/webpack/src/index.js:27:11)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
... etc ...
Desired functionality.

Our build tool cannot crash out of the blue, having changed nothing at all in our code or configurations.  Running npm install with specific versions listed for every package in the package.json should not crash the build machine, and every machine of every developer unfortunate enough to have run "npm install" locally.
Mention any other details that might be useful.

Same issue

I encountered the same issue
Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".
Error: Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".
at Object. (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/@ngtools/webpack/src/index.js:27:11)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/models/webpack-build-typescript.js:5:17)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/models/webpack-config.js:2:34)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/tasks/build-webpack.js:6:24)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/commands/build.js:3:23)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Class.includedCommands (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/addon/index.js:21:16)
at /home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/angular-cli/lib/models/project.js:392:61
at Array.forEach (native)
at Project.addonCommands (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/angular-cli/lib/models/project.js:391:15)
at Project.eachAddonCommand (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/angular-cli/lib/models/project.js:426:30)
at module.exports (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/angular-cli/lib/cli/lookup-command.js:33:13)
at CLI. (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/angular-cli/angular-cli/lib/cli/cli.js:34:26)
at tryCatch (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/rsvp/dist/rsvp.js:539:12)
at invokeCallback (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/rsvp/dist/rsvp.js:554:13)
at publish (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/rsvp/dist/rsvp.js:522:7)
at flush (/home/rxjs/work/ng2-tdd/angular-tdd/node_modules/rsvp/dist/rsvp.js:2414:5)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)

The project needs a dev dependency for @angular/compiler-cli.
npm install --save-dev @angular/compiler-cli@<your angular version>

Thank you @clydin That was correct. I migrated angular-cli from beta to rc.0 and this step was not part of the steps.

any update? i am facing the same issues.

any update ? i also have the same issues

yes, follow @clydin 's response...

but right now i am using angular-cli v1.0.0-beta.17, and i found that the @ngtools/webpack requires 2.3.1. i have tried to upgrade the cli to a higher version, it will throw plenty of exceptions. i just wanna stick with the ready to build version, rather than upgrade all the version.

there is my package.json
		{
		  "name": "olt-storefront-ng2",
		  "version": "0.0.0",
		  "license": "MIT",
		  "angular-cli": {},
		  "scripts": {
			"start": "ng serve --host <IP_ADDRESS>",
			"prod": "ng serve --prod",
			"lint": "tslint \"src/**/*.ts\"",
			"test": "ng test",
			"pree2e": "webdriver-manager update",
			"e2e": "protractor",
			"dist": "ng build --prod && export DATE=`date +%s` && mv dist/inline.js dist/inline.$DATE.js && sed -i.bak \"s/inline\\.js/inline\\.$DATE\\.js/g\" dist/index.html"
		  },
		  "private": true,
		  "dependencies": {
			"@angular/common": "~2.0.0",
			"@angular/compiler": "~2.0.0",
			"@angular/core": "~2.0.0",
			"@angular/forms": "~2.0.0",
			"@angular/http": "~2.0.0",
			"@angular/platform-browser": "~2.0.0",
			"@angular/platform-browser-dynamic": "~2.0.0",
			"@angular/router": "~3.0.0",
			"angular-cli": "1.0.0-beta.17",
			"angular-pipes": "5.5.2",
			"angular2-uuid": "1.1.0",
			"core-js": "^2.4.1",
			"intl": "^1.2.5",
			"moment": "^2.16.0",
			"ng2-meta": "2.0.2",
			"ng2-page-scroll": "^4.0.0-beta.4",
			"ng2-pipes": "0.4.16",
			"ng2-responsive": "0.6.4",
			"rxjs": "5.0.0-beta.12",
			"ts-helpers": "^1.1.1",
			"zone.js": "^0.6.23",
			"dompurify": "^0.8.5"
		  }
		}

the root problem is 1.0.0-beta.17 angular-cli using  "@ngtools/webpack": "latest", and which the latest is not compatible to the "angular-cli": "1.0.0-beta.17", please fix!

Same for 1.0.0-beta.18. A compiler-cli dev dependency (our angular version is 2.1.1) as suggested by @clydin does not work.

Can confirm that @clydin's method seems to require a whole bunch of other peer dependancy changes when using 2.1.0

my problem is in this file
https://github.com/angular/angular-cli/blob/v1.0.0-beta.17/packages/angular-cli/package.json
how can the @ngtools/webpack using latest?

npm install --save-dev<EMAIL_ADDRESS>Horrible hack but at least gets it working short of upgrading all your other packages.

@aeacusvol that worked for me, thanks!

Unfortunately, the fix I suggested can only solve the case of the undefined version.
For those using beta versions, it is strongly recommended to upgrade to the latest RC.  Due to the inherent nature of beta versions, active support of past beta versions is not currently viable.  There is also an extensive list of bug fixes and feature improvements since the early betas.
For those interested in upgrading, there is a guide detailing the necessary steps which can be found here: https://github.com/angular/angular-cli/wiki/stories-rc-update
If while following the guide any deficiencies are encountered, please open an issue so that the guide can be as complete and straightforward as possible.

@aeacusvol's solution no good on<EMAIL_ADDRESS>for me at least

@mildfuzz are you building with global installation of cli? You might need to npm install --g<EMAIL_ADDRESS>in that case

@clydin actually your solution doesn't work for me, since i am doing clean CI build every time, once your dependency is broken all the CI build will be broken. so please help to correct this issue.

--save-dev adds the package to your devDepedencies.  You only need to do it once.

@clydin your recommended fix (adding a dev dependency for @angular/compiler-cli) makes no difference in the result for me:
  "dependencies": {
    "@angular/common": "2.1.2",
    "@angular/compiler": "2.1.2",
    "@angular/core": "2.1.2",
    "@angular/forms": "2.1.2",
    "@angular/http": "2.1.2",
    "@angular/platform-browser": "2.1.2",
    "@angular/platform-browser-dynamic": "2.1.2",
    "@angular/router": "3.1.2",
    . . .
  },
  "devDependencies": {
    "@angular/compiler-cli": "2.1.2",
    . . .
  }

> ng serve --environment=local

Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".
Error: Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".

Open to other suggestions. I am on a beta version of the CLI (18 to be precise), and if upgrading to the latest CLI, which seems also to require updating a whole bunch of angular dependencies is the only way to fix this, then I am going to be very unhappy.  Half dozen separate but dependent projects all have to be coordinated with the version updates, and inevitable issues that go along with those.  Darn good thing I didn't try this before my big demo yesterday.  :/
I agree with the earlier sentiment expressed that this must be a repeatable process.  If it worked a week ago (which it did), it should work today (which it doesn't), especially when there were no dependency changes in between.  I'm not sure how it's even possible to make it fail like this, unless the npm versioning system means absolutely nothing.

Since you're on an old version of angular and a very old beta of the CLI you'll need to use @aeacusvol suggestion instead.
For beta.18 the version of @ngtools/webpack should be 1.1.2.
npm install --save-dev<EMAIL_ADDRESS>

@clydin thanks for the tip, but unfortunately that doesn't work either.  Exactly the same result.  I guess I've got YAAVU (Yet Another Angular Version Update) to slog through now.  You understand my point about how if this worked once it should always work, right?  This worked just fine a week ago. Now it doesn't.  And no changes to our dependencies in between.  The process has to be repeatable or the whole npm packaging and versioning system cannot be trusted.
The only way I can think of for it to break like this is if someone publishes a package with breaking changes without rev-ing the version number or bothering to say anything about it.  And that someone was not me.  But I'm picking up the pieces.
And to your comment about my "very old" verison of angular, let's be very precise: that was 6 months ago.  Not exactly a geological age.

@aeacusvol nope, my deploy task specifically targets the version within the package modules folder:
"compile": "node node_modules/angular-cli/bin/ng build --prod"

Heya, I just want to chime in even though @clydin has already offered a number of solutions.
This issue is related to https://github.com/angular/angular-cli/pull/5118, and the fact that on older versions of the CLI the @ngtools/webpack dependency was rather loose.
We've since fixed @ngtools/webpack to not be as loose. The @angular/compiler-cli dependency has also been there for a while now, and is explicitly mentioned in https://github.com/angular/angular-cli/wiki/stories-rc-update.
I'm sorry that this release wrecked havoc in older releases, and that it has caused you to have to spend time updating and fixing packages.
This isn't something that you can expect to be fixed without an update on your side though. I'm sorry but it's just not. beta.18 and beta.28.3 are versions that were never meant to be supported long term and we never tried to hide that. The only version for which there is long term support is 1.0 when it is out.
The only solution that I think can help really old versions is to force the @ngtools/webpack version as @clydin recommended.
I'd also like to highlight this comment:

You understand my point about how if this worked once it should always work, right? This worked just fine a week ago. Now it doesn't.

I understand that this is desirable. But you do not get that guarantee out of the box with npm. You need to either use npm shrinkwrap or yarn to have reproducible dependency installs.

Got my beta.21 working again thanks to @aeacusvol's solution

So how about updating angular CLI, then just starting a new app and using the packages from the new app?

@filipesilva points all received and accepted here but it's a huge bummer when these things happen (I've come to assume they are unfortunate but inevitable when working with node + npm). While it sucks, the versions facing the issue were clearly beta and so people need to accept the fact that they may encounter issues and not receive long term support.
npm shrinkwrap however does not help with this one due to the very loose latest tag that was used.  We use shrinkwrap with our project and the issue still occurs.  Oh well, an Angular + Angular CLI upgrade was overdue for us anyways... 😉

I have a solution if you aren't ready to upgrade angular-cli or @angular/cli.
It can be done using shrinkwrap and some hoop-jumping. Even though some hackery is invloved, it does result in a fileset that can perform a fresh build from source.

npm uninstall -g angular-cli (getting rid of global instance as we won't be shirnkwrapping that).
npm cache clean
(at this point I'm assuming you currently have your desired version of angular-cli installed in your project's node_modules)
Delete the 'webpack' folder from \node_modules@ngtools and replace it with a version that you know works (in my case this was 1.1.4)
Manually edit \node_modules\angular-cli\package.json and change the dependency from "@ngtools/webpack": "latest" to "@ngtools/webpack": "1.1.4" (bear with me - this is only temporary)
npm shrinkwrap

That's it, now shrinkwrap.json will contain the locked down dependenies that will work for you! From here you should be able to delete node_modules and do 'npm install' successfully.
One more thing, because we're now using a local version of 'ng', you'll need do update your 'scripts' section of package.json - replace any reference to 'ng' with 'node node_modules/angular-cli/bin/ng'. Also as @mildfuzz points out, you might want to add a script line for compile, eg:-
"compile": "node node_modules/angular-cli/bin/ng build"

I did upgrade to the new cli (1.0.0) following the provides steps:
npm uninstall -g angular-cli
npm uninstall --save-dev angular-cli
To update Angular CLI to a new version, you must update both the global package and your project's local package.
Global package:
npm uninstall -g @angular/cli
npm cache clean
npm install -g @angular/cli@latest
Local project package:
rm -rf node_modules dist # use rmdir /S/Q node_modules dist in Windows Command Prompt; use rm -r -fo node_modules,dist in Windows PowerShell
npm install --save-dev @angular/cli@latest
npm install
but I still get the error
Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".
Just to make sure I tried everything I did:
npm install --save-dev<EMAIL_ADDRESS>but to no avail.
This is my package.json if it's any help
{
"name": "datadesk-frontend",
"version": "0.0.0",
"license": "MIT",
"angular-cli": {},
"scripts": {
"start": "ng serve -port 4200 -open",
"lint": "tslint "src/**/*.ts"",
"test": "ng test",
"pree2e": "webdriver-manager update",
"e2e": "protractor"
},
"private": true,
"dependencies": {
"@angular/common": "2.4.0",
"@angular/compiler": "2.4.0",
"@angular/core": "2.4.0",
"@angular/forms": "2.4.0",
"@angular/http": "2.4.0",
"@angular/platform-browser": "2.4.0",
"@angular/platform-browser-dynamic": "2.4.0",
"@angular/router": "3.2.3",
"core-js": "^2.4.1",
"rxjs": "5.0.0-beta.12",
"ts-helpers": "^1.1.1",
"zone.js": "^0.6.23"
},
"devDependencies": {
"@angular/cli": "^1.0.0",
"@angular/compiler-cli": "^2.2.3",
"@types/jasmine": "2.5.38",
"@types/node": "^6.0.42",
"codelyzer": "~2.0.0-beta.1",
"jasmine-core": "2.5.2",
"jasmine-spec-reporter": "2.5.0",
"karma": "1.2.0",
"karma-chrome-launcher": "^2.0.0",
"karma-cli": "^1.0.1",
"karma-jasmine": "^1.0.2",
"karma-remap-istanbul": "^0.2.1",
"protractor": "4.0.9",
"ts-node": "1.2.1",
"tslint": "^4.0.2",
"typescript": "~2.0.3",
"webdriver-manager": "10.2.5"
}
}

The solution @joshdanhall suggested works for me.

There are some environment settings that have to be changed as well in /angular-cli.join
I would share but I'm not at my computer!!! Sorry.
When I: ng serve, the prompt responded with the chages I needed.
But to get to that point, I just built a new app: ng new , then copied over the node modules, and pasted in the new dependencies to my existing package.json
After that, I: ng serve - after that I got the response with the environment setting changes and vwa-la!

.json *

FYI:  as we're upgrading modules for RC4 compliance we temporarily tweaked the broken build to use an unzipped node_modules from a working build (luckily preserved on several dev boxes)  instead of running npm install.  This buys you time to keep adding/building the old code while you upgrade a new branch to use angular-cli RC4 (and beyond).

Yep, same problem here, I did similar thing as @Cogitaria, created .tbz2 from working node_modules directory on dev machine, commited it (unfortunately) and tweaked CI to unpack this archive instead of npm install. Should give us some time before upgrading (if ever...).

Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined"
Even I am facing the same issue while installing CLI version 1.0.0-beta-20-4. Please let me know how can resolve this issue
Thanks in Advance

#Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".
i found this issue , when i upgraded angular cli and create a new project , after run ng serve command this error occurred . please help me what can i do right now in this situation

Same problem here:
Ubuntu 16.04
Node 7.7.3
Npm 4.4.4
After execute npm install -g @angular/cli
ng new project
cd project
ng serve

Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "undefined".
...and it fails to serve! Sad, I just got into Angular to learn this new hype... :-1:
Thought it was mature enough to prevent this type of problems.

I'm using Angular 2, I guess, problem solved! Sort off...
Google is my friend... hehehehehe
Well, I exec this sets of commands
npm uninstall -g angular-cli @angular/cli
npm cache clean
npm install -g @angular/cli@latest
npm install --save-dev angular-cli@latest
npm install --save<EMAIL_ADDRESS>
The current angular-cli create a new Angular2 project, so the @angular/compiler-cli must be 2... version, right?
Ok, now the ng server runs without the problem above. But it's throwing me another error:
patterns.map is not a function

Thing I need more google now...

Cannot install<EMAIL_ADDRESS>it keeps falling to 1.0.0-beta.17

you should have to uninstall angular cli properly then after install again
angular cli
npm install -g @angular/cli
On Wed, May 3, 2017 at 6:23 AM, Jonathan Prass Martins <
<EMAIL_ADDRESS>wrote:

Cannot install<EMAIL_ADDRESS>it keeps falling to 1.0.0-beta.17
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/5558#issuecomment-298803909,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXkePVagBZcg1_sPpx1RuNaGsumLhMkOks5r19ctgaJpZM4Mklhk
.

--
ATTA UR REHMAN
<EMAIL_ADDRESS>Software Developer

I think you shoud update  to angualr cli 1.0 :
npm uninstall -g @angular/cli
npm cache clean
npm install -g @angular/cli@latest
remove local project package:rm -rf node_modules dist  # use rmdir on Windows
then install angular cli  locally in your repo : npm install --save-dev @angular/cli@latest
finally : npm install
you should read over  this for further infos: stories 1.0 update

After uninstall it type "which ng" and remove the symlink. The installation should create a new one pointed to the correct path.

I have node 6.11.0 and ubuntu 14.04 but it is not installing angular cli I am getting following error
`npm ERR! git clone --template=/home/saqlain/.npm/_git-remotes/_templates --mirror git@github.com:angular/cli.git /home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032: Cloning into bare repository '/home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032'...
npm ERR! git clone --template=/home/saqlain/.npm/_git-remotes/_templates --mirror git@github.com:angular/cli.git /home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032: Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
npm ERR! git clone --template=/home/saqlain/.npm/_git-remotes/_templates --mirror git@github.com:angular/cli.git /home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032: Permission denied (publickey).
npm ERR! git clone --template=/home/saqlain/.npm/_git-remotes/_templates --mirror git@github.com:angular/cli.git /home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032: fatal: Could not read from remote repository.
npm ERR! git clone --template=/home/saqlain/.npm/_git-remotes/_templates --mirror git@github.com:angular/cli.git /home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032:
npm ERR! git clone --template=/home/saqlain/.npm/_git-remotes/_templates --mirror git@github.com:angular/cli.git /home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032: Please make sure you have the correct access rights
npm ERR! git clone --template=/home/saqlain/.npm/_git-remotes/_templates --mirror git@github.com:angular/cli.git /home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032: and the repository exists.
npm ERR! Linux 4.4.0-78-generic
npm ERR! argv "/home/saqlain/.nvm/versions/node/v6.11.0/bin/node" "/home/saqlain/.nvm/versions/node/v6.11.0/bin/npm" "install" "-g" "angular/cli"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code 128
npm ERR! Command failed: git clone --template=/home/saqlain/.npm/_git-remotes/_templates --mirror git@github.com:angular/cli.git /home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032
npm ERR! Cloning into bare repository '/home/saqlain/.npm/_git-remotes/git-github-com-angular-cli-git-05516032'...
npm ERR! Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
npm ERR! Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
`

I get this error using VS Code on Zorin Linux (Ubuntu 16.04):
It says that it needs to be 2.3.1 or higher, but doesn't accept 5.05!
Exception has occurred: CLR/System.AggregateException
An exception of type 'System.AggregateException' occurred in System.Private.CoreLib.dll but was not handled in user code: 'One or more errors occurred.'
 Inner exceptions found, see $exception in variables window for more details.
 Innermost exception 	 Microsoft.AspNetCore.NodeServices.HostingModels.NodeInvocationException : Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "5.0.5".
Error: Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "5.0.5".
    at Object.<anonymous>

Can any body help me on this... atleast help me to understand why this error message is coming..
Error: Version of @angular/compiler-cli needs to be 2.3.1 or greater. Current version is "8.2.13".
at Object. (C:\Users\vijasahu\OneDrive - AMDOCS\Backup Folders\Desktop\assets\node_modules@ngtools\webpack\src\index.js:27:11)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:643:32)
at Function.Module._load (internal/modules/cjs/loader.js:556:12)
at Module.require (internal/modules/cjs/loader.js:683:19)
at require (internal/modules/cjs/helpers.js:16:16)
at Object. (C:\Users\vijasahu\OneDrive - AMDOCS\Backup Folders\Desktop\assets\node_modules@angular\cli\tasks\eject.js:10:19)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:643:32)
at Function.Module._load (internal/modules/cjs/loader.js:556:12)
at Module.require (internal/modules/cjs/loader.js:683:19)
at require (internal/modules/cjs/helpers.js:16:16)
at Object. (C:\Users\vijasahu\OneDrive - AMDOCS\Backup Folders\Desktop\assets\node_modules@angular\cli\models\webpack-configs\styles.js:6:17)
at Module._compile (internal/modules/cjs/loader.js:776:30)
PS C:\Users\vijasahu\OneDrive - AMDOCS\Backup Folders\Desktop\assets>

The project needs a dev dependency for @angular/compiler-cli.
npm install --save-dev @angular/compiler-cli@<your angular version>

Hi @clydin tried that no solution


Update README.md

update to correct chart name

Looks good. Any chance you will sign the CLA?

I've tried several times and never get an email to sign. I signed up for hellosign and don't see the document.

Sorry for the inconvenience. Closing for now please re-open if/when the CLA issues are figured out.


Allow use of private registries

I would like to use package-bundle together with a private registry, frankly the npm registry https://registry.npmjs.org/ is hardcoded :-/
I would suggest to:

either to interpret the .npmrc
or introduce a --registry cli parameter
or both :-)

to configure the registry being used.

@stephandrab Good idea! I would be happy to merge a PR for this, or I could potentially look into it sometime next week.

this would be great.


Implement SessionHandler

Refer to Account-Management.drawio in Utilities.

363a201 and fd3f5ac are mistagged and should be in #2


Lingering Friends/Mutes Cleanup

Adds test that exposes remnant data

Closes #35

@Teifion I'm on my way to just understanding the scope of the issue and as part of that I wanted to start with a test that exposes the problem. This is what I have come up with, does this test expose the full issue as you understand it as well or have I missed anything?

This has now been addressed in a recent change to the way friends work.


[Feature request] Start/stop service when bluetooth connect/disconnect

Hi,
is it possible to start the service or stop when a particular bluetooth is connected/disconnected.
This could open the automatic registration of tracks.
Thanks for your beautiful plugin

Honestly, This feature is out of scope for this plugin. But I think this could be done inside your app, without any change in the plugin;


Added godoc for exported blob client methods and types

Rearranged several methods like DeleteBlobIfExists and decided to not to export getProperties() methods.
Closes #4.

cc: @paulmey

LGTM


Ionic Deploy not injected on Android release

Hello All,
I am trying to build a release for android but it seems that the deploy and native are not injected or loaded correctly for some reasons, it happens only on the release while it works perfectly on the debug version. And my first question is why???!!!
ionic build android --prod --release

I tried to import the Deploy in the app.module, service.ts and page.ts but there is always an error.
import { CloudSettings, CloudModule, Deploy } from '@ionic/cloud-angular';

@NgModule({
  declarations: [
    MyApp,
    Page1,
    Page2
  ],
  imports: [
    IonicModule.forRoot(MyApp),
    CloudModule.forRoot(cloudSettings),
    TranslateModule.forRoot({
      provide: TranslateLoader,
      useFactory: translateLoaderFactory,
      deps: [Http]
    }),
  ],
  bootstrap: [IonicApp],
  entryComponents: [
    MyApp,
    Page1,
    Page2
  ],
  /* With or without Deploy in providers is the same */
  providers: [{provide: ErrorHandler, useClass: IonicErrorHandler},Deploy,Storage,TranslatorService]
  providers: [{provide: ErrorHandler, useClass: IonicErrorHandler},Storage,TranslatorService]
})

// service.ts
import { Injector, Injectable } from '@angular/core';
import { Deploy } from '@ionic/cloud-angular';
import { LoadingController, Loading } from 'ionic-angular';

@Injectable()
  export class UpdateController {
    constructor(private _deploy: Deploy, private _loadingCtrl: LoadingController) {
      console.log('UpdateController', this._deploy);
      this._deploy.channel = "dev"; // it's undefined
    }
  }

// page.ts
import { Deploy } from '@ionic/cloud-angular';

private _deploy: Deploy = this._injector.get(Deploy);

constructor(public navCtrl: NavController, private _injector: Injector) {
  console.log('Page1', this._deploy);// undefined
}

Any clue?

This sounds more like a problem than a real issue. I suggest you create a topic on the Ionic Forum at https://forum.ionicframework.com/ and close this issue here. Thanks.

Hi @piotrowski I already open an issue on the forum and I am not the only one, I guess that something it is not working, I didn't try to do a fresh installation of the framework to see if it is going to solve it.
Cordova CLI: 6.5.0
Ionic Framework Version: 2.3.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.4
ios-deploy version: 1.9.0
ios-sim version: 5.0.8
OS: macOS Sierra
Node Version: v6.7.0
Xcode version: Xcode 8.3.2 Build version 8E2002

Then provide a link to your forum post, please.
Here is also the wrong package, as this is @ionic/cloud and not @ionic/cloud-angular.

hi @piotrowski this is the link and I am not the only one.
https://forum.ionicframework.com/t/build-android-with-release-and-prod-make-an-unstable-apk/79760

... which is a topic with 3 unrelated problems all mixed into one post. If you want someone to debug your problem, create a new topic and include all the relevant information.

hi @piotrowski not really the problem that i was facing it is related to the fact that the ionic deploy instance it was always undefined when building an app using the --prod and --release flag together. I didn't ask to debug my problem!

There are dozens of apps out there in the app stores using --prod --release.
So if you have a problem with this combination, please provide a link to a forum topic that includes all the necessary information to your situation. This is not an issue with @ionic/cloud-angular (and surely not with @ionic/cloud where you opened this issue).


support for quantization and qlora models?

would love to use this with quantization and adapters

I am not a maintainer.
This is a duplicate of https://github.com/vllm-project/vllm/issues/744

I am using vllm with qlora. I merge the adapters with
model_for_merge = AutoModelForCausalLM.from_pretrained(
        base_model_path_or_name,
        torch_dtype=torch.float16,
    )
    full_model = PeftModel.from_pretrained(model_for_merge,
                                          model_id=script_args.adapter_dir,
                                        )
    full_model = full_model.base_model.merge_and_unload()
    full_model.save_pretrained(script_args.full_model_dir)
    tokenizer.save_pretrained(script_args.full_model_dir)

and point vllm to this dir. Given that the A & B matrices are added to original weight matrices, there is no change in dimension or architecture.  So, vllm can consume it. I would like a way to pass the model directly after load without saving it though

Closing in favour of #3225 because quantization and LoRA are both supported. We just need QLoRA support.


src: Check header modified by ftrace or sth before install

Backoff when there's already ftrace on a function. Because if we insist on
overwritting function header, ftrace gets confused about its meta data and
may panic the kernel.
Ftrace and other similar infrastructures use call and jmp to do dynamic
patching. So we compare the first byte against 0xe8/0xe9 to see if we
should back off. For now, only x86-64 arch is supported.

/retest

/retest

/retest

/retest

/retest


[WIP] v2 Preview 7.1

Some changes and fixes, mostly styling related:

Switched to FABorder or FAContentPresenter in DatePicker, TimePicker, DropDownButton, and SplitButton and all "Overlay" controls (flyouts, popups, ContentDialog, and TaskDialog when in overlay mode)

NOTE: This only applies to the root border that has the BorderBrush/Thickness applied. To reiterate from the preview7 PR, the changes to FAContentPresenter require no changes on your part. The change to FABorder only requires and update if you have custom styles for one of these controls (just have to update from Border to ui|FABorder, where ui is your xmlns prefix)

Removed the foreground setter on the Header ContentPresenter for NumberBox.
Fixed an issue where a NavigationViewItem without an Icon should show the content aligned as if an Icon was present. Issue was caused by {Binding} in a ControlTemplate is still being applied with LocalValue
Added the new Scroll-related properties to ListBox/TreeView
Removed the obsolete APIs from FluentAvaloniaTheme

RequestedTheme, RequestedThemeChanged, and InvalidateThemingFromSystemThemeChanged are now removed
Also removed the two constructors that required parameters as they're no longer necessary

Cut down on a couple warnings

Known issues caused by things upstream:

ComboBox won't display its last item (will be fixed by 11127)
CommandBarButtons Label text is left aligned (if label is displayed on bottom) - related to 11125 and will be fixed by 11066

Note: branch is not yet on a CI build, I'm going to wait for at least 11127 before merging and releasing a preview7.1

@RobertBeekman Thanks for finding that - fixed it. Once again I forgot to remove the fields after switching from DirectProperty -> StyledProperty.
I've also gone ahead and just pushed out the CI build change that I'm on. That should also fix DevTools since that has the DevTools fix (Dev tools is broken in preview7)

Preview 7.1 was just pushed to nuget - (most likely) requires CI Build 0034035 (most recent to this post).
Contains everything listed above, as well as #354 and #355.


Firefox use default profile

It can be useful to have firefox use the default profile by default, specifically when configuring local certificates for network requests.
Perhaps consider changing this default?

I'm currently trawling through selenium / Firefox docs working out how to change this, even just documenting it could help.

My thinking has been that it makes to have a clean-room browser by default, so that extensions etc. won't interfere with the benchmark. (This is also the Selenium default). I could definitely see a "useDefaultProfile: true" or similar setting, though, which would know how to do that for all browsers.
We do have instructions for changing profiles in Chrome using the addArguments setting: https://github.com/Polymer/tachometer#profiles
However, it seems that we don't currently support addArguments for Firefox. I'll add that, test out profile switching, and update the docs.

However, it seems that we don't currently support addArguments for Firefox. I'll add that, test out profile switching, and update the docs.

This would be an absolutely massive help thanks for considering it. Even just persisting a unique profile that can be shared between runs would be fine as well, the annoying part is having to uniquely update the certificate chain on each run.

I've added a new browser.profile setting in https://github.com/Polymer/tachometer/pull/226, which works for Firefox and Chrome. I also fixed the addArguments bug, though you shouldn't need that now that browser.profile exists.
I also published a pre-release version so you can test this out early: npm i<EMAIL_ADDRESS>Would love to hear if it works for you. It worked for me so far on macOS and Linux.


build(deps-dev): pin dependency pre-commit to 2.4.0

This PR contains the following updates:

Package
Type
Update
Change

pre-commit
dev-dependencies
pin
^2.1.0 -> 2.4.0

:pushpin: Important: Renovate will wait until you have merged this Pin PR before creating any upgrade PRs for the affected packages. Add the preset :preserveSemverRanges your config if you instead don't wish to pin dependencies.

Renovate configuration
:date: Schedule: "on the 1st day of the month,on the 2nd day of the month,on the 3rd day of the month" in timezone Asia/Shanghai.
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

:warning: Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
:recycle: Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you check the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: poetry.lock

/bin/sh: 1: poetry: not found


scrollbar flicker

https://codesandbox.io/p/sandbox/nice-glitter-7t4q6l?file=%2Fsrc%2Fcomponents%2FHelloWorld.vue%3A8%2C1

I can fix that problem using this css, but i think it must be bug


PacketInLogin.java:61-62: Add Server_To_Client_Handshake...

The puzzle 1-d9e1e50c from #1 has to be resolved:
https://github.com/shiruka/shiruka/blob/a80bae3326a07eeda14f1428399b4deef5ac061d/src/main/java/io/github/shiruka/shiruka/network/packets/PacketInLogin.java#L61-L62
The puzzle was created by Hasan Demirtaş on 04-Jan-21.
Estimate: 60 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 1-d9e1e50c has disappeared from the source code, that's why I closed this issue.

The puzzle 1-d9e1e50c has disappeared from the source code, that's why I closed this issue.


Provide some way to manually override IP address configuration

My Sandstorm server's on a static IP that won't change, ever. Therefore, it'd be useful for me to be able to override Sandcats' dynamic DNS service with my own value. This is particularly useful because then Sandcats can respond with really high TTL values for DNS records.

Hi Alex,
Is sandcats as-is assigning you a different IP than the one you'd prefer? Or is high TTL the main benefit here? Do you feel the low TTL is a problem for users or are you worried about load on the sandcats server?

@kentonv Sandcats is, in fact, assigning an incorrect address. That being said, it's due to a known local network misconfiguration, and not because of a bug in the protocol.
Low TTL isn't an issue, per se, but it seems silly to lose the speed and load benefits of high TTL.

Having now looked at the way the Sandcats protocol works, this doesn't seem like it's something we can feasibly support - at least not in a safe way. However the high TTL issue still remains, so retitling appropriately.


ConfigureLinkAttributes not available in v0.7?

Using swift 3, custom types seem to be ignored. Using pattern \ssomeword \b

pod install doesn't install the version in master

The pattern you pass in is treated as a Regular Expression. So there's probably something wrong with it 🤔

Also, adding new custom types does not update the label ATM. Please check that


Move to generic subscripts in Swift 4

Since now generic subscripts have been introduced I think we should be aiming to move the API to them as this cleaner and simpler. For example:
let jsonDictionary: [String: Any] = ...
let value: String? = jsonDictionary[keyPath: "data.name"]

Would replace:
let jsonDictionary: [String: Any] = ...
let value: String? = jsonDictionary.json(atKeyPath: "data.name")

Unfortunately subscripts can't throw yet :/

That's a shame, I was hoping this feature would be introduced Swift 4, maybe next year.


Move Arm connection string provider into impl package

As title. To address this review comment https://apiview.dev/Assemblies/Review/e1da11207fc44c109d78d5d10f697840:

It seems that ArmConnectionStringProvider is just used to manage two references to dependencies which are then used in subtypes mostly anyway. Is there any scenario where user would use this type directly? If no I suggest to absorb those two references to subtypes directly - there doesn't seem to be enough logic inside this type to justify it's existence on public surface otherwise.

LGTM.


archive node retries

Added retry logic for database writes to support concurrent database transactions (described here). This also requires setting transaction isolation level to 'serializable' and can be done in two ways:

set it as the default isolation level in postgresql.conf:
default_transaction_isolation = 'serializable'
set it for a specific database using the following query
ALTER DATABASE <DATABASE NAME> SET DEFAULT_TRANSACTION_ISOLATION TO SERIALIZABLE ;

They need to be done as a separate step before archive node starts writing (and before bringing up the database instance in the case of option 1). I think setting it at the db level makes it explicit and therefore is a better option, but i'm not quite sure where in the codebase this configuration needs to live

Can you confirm that make archive_blocks still builds (there are additional arguments to the make_block_*_aux functions)?

Can you confirm that make archive_blocks still builds (there are additional arguments to the make_block_*_aux functions)?

Can you confirm that make archive_blocks still builds (there are additional arguments to the make_block_*_aux functions)?

Can you confirm that make archive_blocks still builds (there are additional arguments to the make_block_*_aux functions)?

There was a type error, fixed it

Can you confirm that make archive_blocks still builds (there are additional arguments to the make_block_*_aux functions)?

Can you confirm that make archive_blocks still builds (there are additional arguments to the make_block_*_aux functions)?

There was a type error, fixed it

2. set it for a specific database using the following query
   `ALTER DATABASE <DATABASE NAME> SET DEFAULT_TRANSACTION_ISOLATION TO SERIALIZABLE ;`

They need to be done as a separate step before archive node starts writing (and before bringing up the database instance in the case of option 1). I think setting it at the db level makes it explicit and therefore is a better option, but i'm not quite sure where in the codebase this configuration needs to live

Agreed and something like below added to archive node's db-bootstrap jobs should work for this:
      - name: update-transaction-isolation-level
        image: bitnami/postgresql
        command: ["bash", "-c"]
        args: ["PGPASSWORD={{ .Values.postgresql.postgresqlPassword }} psql --username {{ .Values.postgresql.postgresqlUsername }} --host {{ tpl .Values.archive.postgresHost . }} --port {{ .Values.archive.postgresPort }} --dbname {{ .Values.archive.postgresDB}} -c ALTER DATABASE {{ .Values.archive.postgresDB }} SET DEFAULT_TRANSACTION_ISOLATION TO SERIALIZABLE ;"]

2. set it for a specific database using the following query
   `ALTER DATABASE <DATABASE NAME> SET DEFAULT_TRANSACTION_ISOLATION TO SERIALIZABLE ;`

They need to be done as a separate step before archive node starts writing (and before bringing up the database instance in the case of option 1). I think setting it at the db level makes it explicit and therefore is a better option, but i'm not quite sure where in the codebase this configuration needs to live

Agreed and something like below added to archive node's db-bootstrap jobs should work for this:
      - name: update-transaction-isolation-level
        image: bitnami/postgresql
        command: ["bash", "-c"]
        args: ["PGPASSWORD={{ .Values.postgresql.postgresqlPassword }} psql --username {{ .Values.postgresql.postgresqlUsername }} --host {{ tpl .Values.archive.postgresHost . }} --port {{ .Values.archive.postgresPort }} --dbname {{ .Values.archive.postgresDB}} -c ALTER DATABASE {{ .Values.archive.postgresDB }} SET DEFAULT_TRANSACTION_ISOLATION TO SERIALIZABLE ;"]

1. set it as the default isolation level in postgresql.conf:
   `default_transaction_isolation = 'serializable'

Alternatively, we can update the postgres settings set in terraform with extended configs like:
postgresqlExtendedConf = {
      default_transaction_isolation ="serializable"
}

1. set it as the default isolation level in postgresql.conf:
   `default_transaction_isolation = 'serializable'

Alternatively, we can update the postgres settings set in terraform with extended configs like:
postgresqlExtendedConf = {
      default_transaction_isolation ="serializable"
}

!approved-for-mainnet

!approved-for-mainnet


cant remove node

when i remove a node version like: nodist -  5.1.0
it tell me : could not read response for https://nodejs.org/dist/index.json
why would it  read  response for https://nodejs.org/dist/index.json  when i remove a nodejs version?

Nice catch! It tries to look for versions matching your version spec (e.g. 5.1.0) and it does that online, by default. It should however use the locally installed versions as a fallback... I'm investigating...

Aaah, got it!


evaluate_task was calling incorrect library for add_aggregate_scores

This addresses the immediate concern in Issue https://github.com/google/BIG-bench/issues/873
However, I worry that something more nuanced might be going on. I would really appreciate Ambrose confirming that this is the only change needed!

This change is certainly correct, I think I must have just missed this change when committing https://github.com/google/BIG-bench/pull/808. My apologies there, I'm not sure how I missed that!


Wrong imports in code-block chapter 3.5 part 3.6

The Arc from imports is not used in the code.
Also the comment Wrap the pool in an Arc smart pointer is slightly misleading, as we are wrapping it in web::Data.
A sidenote, I have spent quite some time trying to figure out what is wrong after forgetting to update Arc to web::Data in the run function. It actually compiled, but the subscribe tests returned status 500 without any more information. Might be worth mentioning it more explicitly in the text, as the related small "exercise" is not so interesting -- the compiler nor the errors are pointing you to the right direction. I started comparing my code to your 1:1 and that is the only way I could find this inconsistency.

I have fixed the unused import and improved the code comment. Thanks for reporting the issue :bow:


fix: stop committing openings of files in store

Aimed for #534, openings of an Alva file can be reverted with undo.
Therefore, I have removed store.commit() from ServerMessageType.OpenFileResponse and ServerMessageType.CreateNewFileResponse in order to ignore these kind of changes for history.

Sounds good! Thanks for contributing!

Hey @barinali and @LKuechler – I just tried it out and run into a little problem – the first action after creating a file/project can’t be undone now. E.g. – I open Alva, Create a project, add a text to the elements and Hit Cmd+Z, the text does not remove any more.
Can we somehow fix this?

@tilmx I'll look at it and try to come up with a solution.


Update card-section-carousel.mdx

update intro section copy
Related Ticket(s)
{{Provide url(s) to the related ticket(s) that this pull request addresses}}
Description
{{Add a human-readable description / detail summary of what the PR is changing and any details around how and why}}
{{If applicable, include a screenshot indicating an example or examples of what the PR is changing in the application}}
Changelog
New

{{new thing}}

Changed

{{changed thing}}

Removed

{{removed thing}}

@jeffchew We are good to go with this update!


Lock mechanism problem

Hi, so here is

debug log.

2018-07-20 11:05:05.002  < mqtt /myhome/status/lock 1 1
2018-07-20 11:05:05.002  > hap update FrontDoorLock LockCurrentState.UNSECURED
2018-07-20 11:05:33.868  < mqtt /myhome/status/lock 0 0
2018-07-20 11:05:33.868  > hap update FrontDoorLock LockCurrentState.UNSECURED

Configuration
"FrontDoorLock": {
"id": "FrontDoorLock",
"name": "FrontDoorLock",
"manufacturer": "",
"model": "BE469",
"services": [
{
"name": "FrontDoorLock",
"service": "LockMechanism",
"topic": {
"setLock": "/myhome/in/command/lock",
"statusLock": "/myhome/state/lock"
},
"payload": {
"lockSecured": "1",
"lockUnsecured": "0"
},
"config": {},
"props": {}
}
Problem. Web ui doesn't have option to configure lockUnsecured payload. Had to add it manually. And lock never updates status when it locks. It gets stuck with "locking status". Tested with 0-1 and ON - OFF payloads.
Could you please test

So does't matter what I publish to mqqt, lock always gets unsecured update.
2018-07-20 11:08:24.012  < mqtt /myhome/status/lock 0 0
2018-07-20 11:08:24.012  > hap update FrontDoorLock LockCurrentState.UNSECURED
2018-07-20 11:08:30.318  < mqtt /myhome/status/lock 1 1
2018-07-20 11:08:30.318  > hap update FrontDoorLock LockCurrentState.UNSECURED

Ok, found problem - https://github.com/hobbyquaker/homekit2mqtt/commit/f2ad7a4e8bf186c0f8ea582ba77f28c64cae2e8a
I am using latest available version. So it looks like bug still exists.

Now,
2018-07-20 11:20:48.710  < mqtt /myhome/status/lock 0 0
2018-07-20 11:20:48.710  > hap update FrontDoorLock LockCurrentState.SECURED
2018-07-20 11:20:57.361  < mqtt /myhome/status/lock 1 1
2018-07-20 11:20:57.361  > hap update FrontDoorLock LockCurrentState.UNSECURED
But, when I publish unlock message 0, HomeKit reports (notification) that lock was unlocked but lock icon spins with locking status.

Hey there, I have the same problem. For the payload "lockUnsecured" there is no input box. If I add it manually the behavior is the same.
The Unlocking process is OK and the locking process works, but the homekit icon in iPhone is still spinning. However a locking command is sent to broker.
It seems like the service is waiting for approve, that it was safety locked.
I 'm a beginner, but could be possible there are more payload needed?
According to Homekit accessory protocol specification, there are in part 8.16 Lock Current State, do you think is it necessary?
Thanks

I see payload settings were added, but HK update problem still exists with latest version.


Screen Sharing, Meeting Recording and Background for react native

Hi, I am fairly new to native programming and have been struggling on implementing the screen sharing, meeting recording and background changing feature in my react native app. I have integrated the sdk and is working for audio/video calls and texts but the example source code has no implementation of the mentioned features. Any help would be appreciated.

Please update if you have found any solution regarding screen sharing @AliBaig-xD

Hi @AliBaig-xD, @equilizer, thanks for reaching out. Our RN sample app covers the basic functionalities with mobile SDKs to demonstrate the idea / structure on how RN customer can use them. However we don't have cadence to demonstrate all features at this time, I'm adding this as a feature request.
If it helps, you can take a look at the related guide on the Android / iOS SDK repo:

https://github.com/aws/amazon-chime-sdk-android/tree/master/guides
https://github.com/aws/amazon-chime-sdk-ios/tree/master/guides

Found a way to implement screen share on Android using Amazon chime SDK.

Found a way to implement screen share on Android using Amazon chime SDK.

Found it ??

yes. Its working!

yes. Its working!

Dude, can you help ?? How did you do it? and does it work on both android and ios??


Feature request: additional info in output of listtermdeposits command

I find useful to have 2 additional fields in listtermdeposits command: account and estimated time.
Changed rpcwallet.cpp function listtermdeposits():
Object entry;
        entry.push_back(Pair("account",ctermDeposit.tx->strFromAccount));

and
time_t rawtime;
        char buffer[16];
        time(&rawtime);
        rawtime += blocksRemaining * 120;
        struct tm * timeinfo = localtime(&rawtime);
        strftime(buffer,15,"%Y/%m/%d",timeinfo);
        entry.push_back(Pair("estimated date",buffer));
        strftime(buffer,15,"%H:%M:%S",timeinfo);
        entry.push_back(Pair("estimated time",buffer));

The report looks like this:
{
        "account" : "TheTDD",
        "status" : "Earning",
        "principal" : 3967.95548766,
        "accrued interest" : 1.05703300,
        "accrued value" : 3969.01252066,
        "on maturation" : 27512.00586655,
        "term " : 262799,
        "deposit block" : 267239,
        "maturation block" : 530038,
        "estimated date" : "2020/02/06",
        "estimated time" : "09:11:26"
    }

Enhancement: rpcwallet.cpp function listtermdeposits():
#76 Add fields listtermdeposits: account and estimated time
Added:
Ln 909 - entry.push_back(Pair("account",ctermDeposit.tx->strFromAccount));
Ln 927-934 - Modified with:
time_t rawtime;
char buffer[16];
time(&rawtime);
rawtime += blocksRemaining * 120;
struct tm * timeinfo = localtime(&rawtime);
    strftime(buffer,15,"%Y/%m/%d",timeinfo);
    entry.push_back(Pair("estimated date",buffer));
strftime(buffer,15,"%H:%M:%S",timeinfo);
entry.push_back(Pair("estimated time",buffer));


[Feature Request] Support ES5 environments

Hi! We'd love to give this a spin, especially the mocking functionality, but are currently unable to because the project only ships ES6 code, and our test environment is running Node 4.

Hey @mikefowler! Do you know which js features it was choking on? In general I tried to make it stick only to the base es2015 feature set. At Pinterest we are on Node 4.4.x and haven't had issues.

Hi @zackargyle! The issue I'm running into is SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode being thrown at the point that I import service-worker-mock into a Jest spec. It's choking on the const declarations in index.js of this package.

Oh interesting. Can we just add "use-strict"; to the top of all the files? If that works, it'd be an easy opportunity to contribute to the project!

"use strict" (no hyphen) would make it work in node 4, but not in node < 4. Is there any reason not to babel-transpile prepublish?

The reason not to was because we didn't need to. If more people want to use the project but can't because of node version requirements, I'm happy to add the transpilation.
Looks like ~70% of Node projects use 4 or above (Node Survey Report. So maybe it is worth transpiling on prepublish for the potential other 30%.

Code that uses Service Workers might also run in browsers which don't support service workers (even though, obviously, it wouldn't be expected to work) - but it would be expected to parse, which const wouldn't do.

@zackargyle, as it turns out, we're updating to Node 6 tonight (🎉), so this likely won't be an issue for us anymore. As you pointed out, though, shipping transpiled would allow more teams to give these libraries a shot.

@mikefowler Any update/issues/requests/problems? Curious if you ended up using any of the tools, and if not, what you went with. Thanks!


fix error when hash contains slash ('/') for v1.

Proposed changes

fix error when hash contains slash ('/').
fix #2848
The same fix for v0.x is in #5291
Screenshots (if appropriate) or codepen:

Types of changes

[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Could you please take time to look at this? From http://www.w3.org/TR/html/dom.html#the-id-attribute, id contains slash is absolutely legal.
And this is such a simple fix that only contains a 3-character change


Modified isRootRef to use monorepo

There is a problem using the plugin in a monorepo environment.
svg files do not run on the plugin because the isRootRef value is true when referring to the svg file in a different directory.
If there is no issue, I hope the pull request will be accepted. thank you
error
index.45b22a28.js:4 DOMException: Failed to execute 'createElement' on 'Document': The tag name provided ('/assets/icn_arrow_up.a3b33b67.svg') is not a valid name.

project/pacakge-common/src/asset/svg/common.svg - is not coverted
project/pacakge-a/src/asset/svg/a.svg - is converted well
project/pacakge-a/index.html

Hi, thanks for your PR!
I'm not sure about this solution. If you'd go back 2 folders, for example, it still won't work.
How do you access the svg icons? Something like ../../package-common/src/asset/svg/common.svg? In that case, we could maybe add a rule when the path starts with ../ then it should not be treated as 'root' url.

Hi, you are right.
if i use ../../. it's not working still.
my PR only works if it starts with ../
i use allias common ex) common/assets/svg/icn_map.svg
in my case:
root: /Users/shane/Desktop/git/project/package-a
id: /Users/shane/Desktop/git/project/package-common/src/assets/svg/icn_map.svg

Actually, I don't know why you check isRootRef and I want you to remove it if possible.
In the case of vue-svg-loader, similar conditions do not exist.

You're right, I've removed the check and added a better solution in v3.4.0

Thanks for your help!


Wrong use of cargo_metadata outside build.rs

TLDR; if you build against this crate and copy the resulting executable anywhere else and run it from there, it will not work. Or uninstall your Rust toolchain and try to run it. It will not work.
Kindly pardon the snarky tone of what follows but this just cost me two hours.
I can't help but think that I must be the first person to actually use the Infobip Rust SDK in production-deployed code.
The fact that this crate sports two error variants called SdkError::RustVersion and SdkError::CargoMetadata seems to suggest that whoever wrote this was likely new to Rust.
Details
Inside src/api/mod.rs, there is this gem:
fn get_user_agent() -> Result<String, SdkError> {
    let rust_version = version()?;
    let cmd = MetadataCommand::new();
    let package_version = cmd
        .exec()?
        .packages
        .into_iter()
        .find(|p| p.name == "infobip_sdk")
        .unwrap()
        .version;

    Ok(format!(
        "@infobip/rust-sdk/{} rust/{}",
        package_version, rust_version
    ))
}

rustc_version::version() will horribly fail if you do not have a Rust compiler installed at run time (an assumption that is at best weird).

MetadataCommand::exec() will fail horribly when used from outside any Rust project folder structure.

The cargo_metadata crate is meant for two use cases:

either inside a cargo subcommand (which will typically only be ran from within a Rust project folder)

or inside build.rs. I.e. to gather static data at compile time.

The same goes for the rustc_version crate.
Neither is meant to be used at run time outside of such contexts. Quote from the top of the README of cargo_metadata (emphasis mine):

Structured access to the output of cargo metadata. Usually used from within a cargo-* executable.

And from the top of the README of rustc_version (emphasis mine):

This can be used by build scripts or other tools dealing with Rust sources to make decisions based on the version of the compiler.

Reproduce
Either:

Copy your SMS example program from /target/debug/<name of the example> to e.g. $HOME and run it from there.
Just uninstall Rust/resp. make sure rustc is not in $PATH before trying to run.

For the former case you will get something like (this is the ? in sms_client.send(request_body).await? unwrapping to an Err):
thread 'main' panicked at src/main.rs:29:56:
called `Result::unwrap()` on an `Err` value: CargoMetadata(CargoMetadata { stderr: "error: could not find `Cargo.toml` in `/home/moritz` or any parent directory\n" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Fix
Now also included in #14.

Hi Moritz. I'm sorry these issues caused you to loose time. This crate is indeed one of our first Rust projects, but we are improving. Thanks for your contributions!

No worries, sorry I was bit grumpy. It was one of those days. :grin:

I'm re-opening as I just realized there is update published on crates.io yet.
All the latest published versions of this crate (0.5.0, 0.5.1 and 0.5.2) on are completely broken for actual production use (i.e. beyond running some examples locally) because of this issue.
I.e. you should at least yank any previous 5.x version from crates.io and ideally also publish 0.5.3 with a fix for this, cherry-picked from #14).


Modify anchor link position

Provide the exact quote of the error or issue
Currently the anchor link is placed to the left of the heading and is covered by the scroll bar.
It would be better to place it to the right of the heading.

Does the docs page already exist? Please link to it.
all pages
Are you willing to participate in fixing this issue and create a pull request with the fix?
None

Fixing It : #1675

@shivamksharma
Hi, thanks for the comment!
Already fixed in #1679 :)


Login issues - post 500 error

Howdy, I've been following the guide completely, Yet despite this I've gotten different types of errors from different things. However now I'm being left with just a post error 500.
Before this current error, it would display

"error at line 22 of /api/app/controllers/Login.php":
if($password==null){ $json_arr['status']="failed";     $json_arr['message']="Password missing"; return json_encode($json_arr);     }

I'm unsure of what my next step would be from here (for the post 500 error, not the code above. That's just to display one of the errors I've gotten and isn't a problem suddenly.)
I am attempting to host this on an ifastnet premium server. If there's any other information you'd like please ask and i'll provide what i can.
Thanks for your time. 👍

I reinstalled it a few times and then it magically started working. i have no idea anymore.


Upgrade Vagrant Playbook Check Host To Ubuntu 24.04

The current vagrant playbook check host is on Ubuntu 18.04.
This is end of life, and requires an update.
Ref: #3588

Checking with @AdamBrousseau to see if a backup or snapshot of the machine is possible, as this is a large upgrade path, it may be problematic, and Im trying to not risk the machine. In the meantime I'll investigate the possibility of just upgrading ansible in the short term.

@steelhead31 @Haroon-Khel and I had a discussion on this today. Given the usefulness of the VPC functionality (and the fact there are some odd entries in the /etc/os-release which appears to show Debian instead of Ubuntu ncontnet) we have decided to avoid attempting to upgrade this server and to prototype a new Ubuntu 24.04 replacement on Azure with a view to using the knowledge gained from doing that to reinstall the existing vagrant server.

Following discussions last week, I've begun creating an azure based vagrant host as a proof of concept.


[BEAM-1534] Create a dockerized developer environment for Beam

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

This pull request introduces docker images mostly for development purposes (to
have a ready to test environment with the Beam source code), it is like a poor man jenkins but this images can neatly be run in a cluster manager like kubernetes to invoke a maven verification script. I end up coding this to validate the release and reproduce bugs e.g. in JDK 7.
Additionally the PR introduces a docker image to have an out of the box distribution with the python SDK that can submit pipelines to Dataflow. We can in the future publish this one into docker hub if there is interest.
R: @jasonkuster @davorbonaci
R: @aaltay for the python bits

Coverage remained the same at 70.474% when pulling 172f77e1de1a716e349ce1bdf5df0cdd3740f86d on iemejia:BEAM-1534-docker into e206b1a41c1f22330cb78fd1082425ea1e74dbb4 on apache:master.

R: @jbonofre

Maybe it could make sense to have different Dockerfile providing Beam + [Flink/Spark] + [Some "default" IOs] ?

I think it's also related to https://issues.apache.org/jira/browse/BEAM-320: the dockerfiles could package existing Beam distros.

Yes @jbonofre the last docker image (the python one) is definitely closer to BEAM-320, and we can eventually make it part of it because it could be clearly be an out of the box 'binary' distribution of Beam. Or at least a template for devs to use.

Wow, this looks awesome! I'll dig into this probably over the weekend or on Monday; does that sound good?

Sure @jasonkuster there are many things here so I understand the review takes some time.

Ok, guys made the changes after the review by @aaltay, mind to take another look. Also @jasonkuster if you have some comments please they are welcome.

Extra note I suppose the README should end up in the website but i will do this once we agree on the PR.

Coverage decreased (-0.5%) to 69.948% when pulling 837e9081729c7da84eb39eaeb2bd62f67ecbf003 on iemejia:BEAM-1534-docker into e206b1a41c1f22330cb78fd1082425ea1e74dbb4 on apache:master.

LGTM, Thank you @iemejia. (Please give a chance for @jasonkuster to review the changes before merging.)

@jasonkuster If you have some time PTAL I will wait for more feedback until the end of the week if you are not available I will merge as it is and we would fix other details after.

Coverage decreased (-0.01%) to 69.967% when pulling 68091296f12ad51523c816954ec593e720733c37 on iemejia:BEAM-1534-docker into 62294e64cb3f68e37cd0ed133070fb617334c09e on apache:master.


[libvpx] Build error

Hello, i am trying to install libvpx for arm-v7a arch but no luck, can someone halps me ? thx.
FYI: When i try to install other packages like libyum or opus with :arm-android it is successfully installed.
Package: libvpx[core]:arm-android -> 1.12.0
Host Environment

Host: x64-linux
Compiler: Clang 11.0.5
vcpkg-tool version: 2022-12-14-7ae0d8527fb488fde10a89c2813802dc9b03b6f9
vcpkg-scripts version: 136ad069f 2023-01-24 (25 hours ago)

To Reproduce
vcpkg install libvpx:arm-android
Failure logs
-- Using cached webmproject-libvpx-v1.12.0.tar.gz.
-- Cleaning sources at /home/ubuntu/vcpkg/buildtrees/libvpx/src/v1.12.0-2729413caf.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/ubuntu/vcpkg/downloads/webmproject-libvpx-v1.12.0.tar.gz
-- Applying patch 0002-Fix-nasm-debug-format-flag.patch
-- Applying patch 0003-add-uwp-v142-and-v143-support.patch
-- Applying patch 0004-remove-library-suffixes.patch
-- Using source at /home/ubuntu/vcpkg/buildtrees/libvpx/src/v1.12.0-2729413caf.clean
CMake Error at ports/libvpx/portfile.cmake:182 (message):
  libvpx does not support architecture arm
Call Stack (most recent call first):
  scripts/ports.cmake:147 (include)

This issue hasn’t been updated in 3 month, if it is still an issue, please reopen this issue.


Docker 1.12.0-rc3 swarm mode - can't make wildfly standalon-ha to register on httpd-modcluster

Output of docker version:
docker version
Client:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 21
 Running: 2
 Paused: 0
 Stopped: 19
Images: 162
Server Version: 1.12.0-rc3
Storage Driver: devicemapper
 Pool Name: docker-202:32-3932161-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 2.345 GB
 Data Space Total: 107.4 GB
 Data Space Available: 102.9 GB
 Metadata Space Used: 8.495 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.139 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2016-06-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay bridge host null
Swarm: active
 NodeID: 01h8iq4kxdlibdw9mdx394jd0
 IsManager: Yes
 Managers: 1
 Nodes: 3
 CACertHash: sha256:04669ba0d6dc01402b667248b5ac3c86319f55d07c34c09f1cbf46320f220b84
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.22.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.792 GiB
Name: VINDOC701.dev1.stelo.local
ID: E7SP:4FWC:HVFL:KIWG:3HIJ:ZXVZ:PYSE:4OZI:KGK7:J2LP:DK6F:XFSY
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.): Physical
Steps to reproduce the issue:
1.
docker node ls
ID HOSTNAME MEMBERSHIP STATUS AVAILABILITY MANAGER STATUS
01h8iq4kxdlibdw9mdx394jd0 * VINDOC701.dev1.local Accepted Ready Active Leader
510vgjvdvq9kk5ufpzb44p7iu VINDOC703.dev1.local Accepted Ready Active
7oq0krop57wfebcgsr8t8bk4t VINDOC702.dev1.local Accepted Ready Active

I have two Docker Images I've built, one for httpd with mod_cluster, and another with Wildfly 10. When I run them on my local machine without Swarm, they work together fine, so when I query mod_cluster_manager, it shows all the Wildfly containers running, and it also load balance http access to node-info app:

dstolf@cherno-alpha:~/docker/wildfly$ docker run -d -p 8080:80 centos/httpd/modcluster
1b2de0f2c0d9867b39246d3cd22efb56676214099d494d6c4106a1a5b511961a

dstolf@cherno-alpha:~/docker/wildfly$ docker run -d jboss/wildfly/app
d60c191a7b72b17690310c6d41e0fb791d20372e54aaf0591f406d659511bb1f

dstolf@cherno-alpha:~/docker/wildfly$ docker run -d jboss/wildfly/app
5bb68830d6bc33210e384989cd8f1233fdaac54ef240c61fd11f2551d6052b4d

dstolf@cherno-alpha:~/docker/wildfly$ docker run -d jboss/wildfly/app
3f234b5174a03d1ff4c2b95d11e4f57a0b44ce479bbefc70e2a3bced03eb7b2f

dstolf@cherno-alpha:~/docker/wildfly$ curl http://localhost:8080/mod_cluster_manager
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<title>Mod_cluster Status</title>

mod_cluster/1.3.1.Final
Auto Refresh show DUMP output show INFO output

 Node server-<IP_ADDRESS> (ajp://<IP_ADDRESS>:8009):

...

So I pulled the originial images (jboss/wildfly and centos/httpd) from official registry into my private registry. When I run them on docker 1.12 with swarm mode active, the Wildfly containers can't communicate with httpd-modcluster and register themselves:

docker service create --replicas 1  -p 3000:80    --mount target=/data,source=/data,type=bind,writable=true --name load_balancer dockerhub.dev1.stelo.local:5000/centos/httpd/modcluster
docker service create --replicas 3  -p 8080:8080   --mount target=/data,source=/data,type=bind,writable=true  --name java_app       dockerhub.dev1.stelo.local:5000/jboss/wildfly/app

4- So, when I go to my browser and try to open on :3000/mod_cluster_manager, there are no containers registered. If I go to :8080/node-info, I get the expected output from the test java app, because I published port 8080.
5- http/modcluster Dockerfile
FROM dockerhub.dev1.stelo.local:5000/centos/httpd
USER root

# Disable mod_proxy_balancer module and enable mod_cluster
RUN sed -i 's|LoadModule proxy_balancer_module|# LoadModule proxy_balancer_module|' /etc/httpd/conf.modules.d/00-proxy.conf

# Add launch.sh
ADD launch.sh /
ADD template_modcluster /
RUN chmod +x /launch.sh

# add mod_cluster
ADD mod_advertise.so /etc/httpd/modules/
ADD mod_manager.so /etc/httpd/modules/
ADD mod_proxy_cluster.so /etc/httpd/modules/
ADD mod_cluster_slotmem.so /etc/httpd/modules/

# Add mod_cluster.conf
ADD mod_cluster.conf /etc/httpd/conf.d/mod_cluster.conf

# Do the required modifications and launch Apache after boot
ENTRYPOINT /launch.sh

5- launch.sh
#/bin/bash

# Get the Hostname
HOSTNAME=$(hostname)
# Adjust the IP addresses in the mod_cluster.conf file
IPADDR=$(hostname -i | awk '{print $2}')
sed -i "s|[0-9\.\*]*:80|$IPADDR:80|g" /etc/httpd/conf.d/mod_cluster.conf

cat template_modcluster >> /etc/httpd/conf.d/mod_cluster.conf

# Log run
echo "######## Start httpd modcluster ########" >> /data/httpd/httpd_${HOSTNAME}.log
hostname >> /data/httpd/httpd_${HOSTNAME}.log
echo $IPADDR >> /data/httpd/httpd_${HOSTNAME}.log
date >> /data/httpd/httpd_${HOSTNAME}.log

# touch error_log and access_log
touch /var/log/httpd/error_log
touch /var/log/httpd/access_log

# tail file and redirect to /data/httpd/
nohup tail -f /var/log/httpd/error_log >> /data/httpd/error_log_${HOSTNAME}.log &
nohup tail -f /var/log/httpd/access_log >> /data/httpd/access_log_${HOSTNAME}.log &
nohup tail -f /var/log/messages >>  /data/httpd/messages_${HOSTNAME}.log &

# dump final mod_cluster.conf

5- template_modcluster
<VirtualHost *:80>

  EnableMCPMReceive true
  ServerAdvertise On
  ServerName loadbalancer

  <Location />
    Require all granted
  </Location>

  <Location /mod_cluster_manager>
    SetHandler mod_cluster-manager
    Require all granted
  </Location>

</VirtualHost>

6- wildfly docker file:
FROM dockerhub.dev1.stelo.local:5000/jboss/wildfly
USER root
# ADD app to deployment folder
ADD node-info.war /opt/jboss/wildfly/standalone/deployments/

# ADD launch script standalone ha mode
ADD launch_standalone_ha.sh /

# Change launch script permission
RUN chown jboss:jboss /launch_standalone_ha.sh

# Change app files permission
RUN chown jboss:jboss /opt/jboss/wildfly/standalone/deployments/node-info.war

# Change launch scripts permissions
RUN chmod +x /launch_standalone_ha.sh

# add wildfly admin user
USER jboss
RUN /opt/jboss/wildfly/bin/add-user.sh admin Admin@123 --silent

# Run WildFly after the container boots
ENTRYPOINT /launch_standalone_ha.sh

7- launch_standalone_ha.sh
#!/bin/bash
# output of hostname -I is <IP_ADDRESS> <IP_ADDRESS>
# already tried to use both of them at the line bellow
IPADDR=$(hostname -I | awk '{print $2}')
touch /data/wildfly/standalone_ha_`hostname`.log
hostname -I > /data/wildfly/standalone_ha_`hostname`.log

# alternate launch #
#echo "/opt/jboss/wildfly/bin/standalone.sh -c standalone-ha.xml -Djboss.bind.address=$IPADDR -Djboss.bind.address.management=$IPADDR -Djboss.node.name=server-$IPADDR" >> /data/wildfly/standalone_ha_`hostname`.log

#/opt/jboss/wildfly/bin/standalone.sh -c standalone-ha.xml -Djboss.bind.address=$IPADDR -Djboss.bind.address.management=$IPADDR -Djboss.node.name=server-$IPADDR >> /data/wildfly/standalone_ha_`hostname`.log
# ############ #

echo "/opt/jboss/wildfly/bin/standalone.sh -c standalone-ha.xml -Djboss.bind.address=<IP_ADDRESS> -Djboss.bind.address.management=$IPADDR -Djboss.node.name=server-$IPADDR" >> /data/wildfly/standalone_ha_`hostname`.log
/opt/jboss/wildfly/bin/standalone.sh -c standalone-ha.xml -Djboss.bind.address=<IP_ADDRESS> -Djboss.bind.address.management=$IPADDR -Djboss.node.name=server-$IPADDR >> /data/wildfly/standalone_ha_`hostname`.log

Describe the results you received:
Wildfly nodes don't register themselves with http-modcluster
Describe the results you expected:
That wildfly nodes should register with http-modcluster

BTW: I'm still learning all this, and I'm also not used to git, so...
I could use unicast, but then it would be impossible to register wildfly worker nodes, because I can't figure out their ip's beforehand.

@DSTOLF could you please explain the wildfly registration process ? Which IP address should you know beforehand in order for the registration to work ?

Hi @mavenugo , how are you?
As far as I understand, wildfly uses multicast to announce itself on the network and get registred on httpd/mod_cluster.
https://docs.jboss.org/author/display/WFLY8/Load+Balanced+HA+Standalone+Cluster+-+Howto

Starting the wildfly instance can be done using the below command on Unix on both the servers
./standalone.sh -c standalone-ha.xml -b=$HOSTNAME -bmanagement=$HOSTNAME -u <IP_ADDRESS> -Djboss.node.name=$HOSTNAME
Here the -c option specifies the configuration file to use. We are going to use the High-Availability setup
The -u option describes the multicast address. It is using this IP both servers communicate.
For ease of setup, I have included the $HOSTNAME in the nodename and start up options

An alternative approache would be to fallback to unicast:
https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Administration_and_Configuration_Guide/Configure_the_mod_cluster_Subsystem_to_Use_TCP.html

The mod_cluster subsystem uses multicast UDP for its network communication by default. If you wish, you can use unicast TCP communication instead. Use the following procedure to configure this behavior.
...
Modify the HTTPD configuration to disable server advertising and to use a proxy list instead. The proxy list is configured on the worker, and contains all of the mod_cluster-enabled HTTPD servers the worker can talk to.

Bu I don't think that would work on Swarm Mode. I don't know the mod_cluster's containers IP address beforehand and, if I scale them out, I won't be able to modify the running Wildfly workers' configurations.

+1 This is exactly what I also would like to achieve!

@DSTOLF with the built-in service discovery, one can easily get the ip-addresses of all the containers that backs a service. For example, if mod_cluster-enabled HTTPD Service is named mod-cluster-service, then a DNS query to tasks.mod-cluster-service will return all the ip-addresses of the containers across the cluster that backs this service. I guess one can use that to configure the unicast method.
Yes. Multicast is not supported yet and using the unicast fallback approach is the only way atm.

@bangnab  I've seen weavenet before, but it seems unstable ATM on 1.12
https://github.com/docker/docker/issues/23990
https://github.com/weaveworks/weave/issues/2403
Global plugins are still unsupported on swarm mode and there are a few issues with local plugins that have been corrected just a few days ago.

@mavenugo
I'll try it out, and get back to you.
But I think it's far from an optimal solution.

I'm not sure if I can put the tasks.mod-cluster-service straight into the proxy list. I think I'll probably have to resolve the name on a shell script and sed the ip addresses list into the configuration files;

But shell scripting is the least of our problems. Say, if I have to scale an httpd/mod_cluster service , I would have to reprovision all the wildfly worker nodes so they could re-register with the new load balancer containers;

Or even worst, the load balancer crashed and restarded, when it get back online, it will have no worker nodes registred to it and I would have to restart the wildfly service.

@DSTOLF am not familiar with how wildfly operates. So, some of my questions/suggestions may not apply directly. But I will still try :-). With swarm-mode, we support VIP based Load-balancing combined with Service-Discovery. Hence the only configuration the applications ideally would need is the Virtual-IP of the service and ideally should not care about the individual containers that back that service. I know it is a very gross generalization of a docker application and may not be applicable for your specific case.
If this particular application absolutely requires individual containers during scaling or such operations, then the only way (in the absence of multicast support) is to learn about the new container and reprogram the configuration.
Regarding your question on plugins,  Yes, swarm-mode doesnt support remote network plugins yet. And swarm-mode can be used only with global-drivers (local-drivers doesnt make much sense if one need multi-host connectivity, which is a basic requirement for swarm-mode). We are working on making the plugins available in swarm-mode post 1.12 release.

@mavenugo I'm also no specialist on Wildfly and Jboss. I'm actually pretty new to it.
For the record, I couldn't set up the damn thing up using Unicast (Wildfly's fault or mine, not Docker's haha)  and httpd mod_cluster. So I decided to go with JGroups and Gossip Router (which is still a single point of failure, but fully compatible with the overlay network) and am now using Swarm Mode own load balancing system.
It's enough for me for the moment to continue with my tests.
But I'd sure wish to see native multicast support on Swarm, or at the very least get plugins supported in swarm-mode. It would be very nice to be able to setup a dynamic JBoss or Wildfly Cluster in Docker in the easy mode

BTW, thanks a lot for your feedback. Keep up the good work.

Thanks for the confirmation @DSTOLF .
Yes. We have a few request for the multicast support. But we havent received any contributions to make that happen :-).

@mavenugo do we have a tracking issue for that? Perhaps we should create one, and add a "help wanted" label

@thaJeztah https://github.com/docker/libnetwork/issues/552 and I added the help/wanted label long ago :)

@DSTOLF should we close this issue in favor of https://github.com/docker/libnetwork/issues/552 ?

Sure, go ahead.

Thanks!


KeyError: 'EpochBasedRunnerAmp is not in the runner registry'

Great work!
When I attempted to run the code, I met such error!
Can someone help me?
fatal: not a git repository (or any of the parent directories): .git
Traceback (most recent call last):
File "tools/train.py", line 187, in
main()
File "tools/train.py", line 183, in main
meta=meta)
File "C:\Users\1\anaconda3\envs\cocodetection\lib\site-packages\mmdet\apis\train.py", line 147, in train_detector
meta=meta))
File "C:\Users\1\anaconda3\envs\cocodetection\lib\site-packages\mmcv\runner\builder.py", line 23, in build_runner
runner = runner_constructor()
File "C:\Users\1\anaconda3\envs\cocodetection\lib\site-packages\mmcv\runner\default_constructor.py", line 44, in call
return RUNNERS.build(self.runner_cfg, default_args=self.default_args)
File "C:\Users\1\anaconda3\envs\cocodetection\lib\site-packages\mmcv\utils\registry.py", line 212, in build
return self.build_func(*args, **kwargs, registry=self)
File "C:\Users\1\anaconda3\envs\cocodetection\lib\site-packages\mmcv\utils\registry.py", line 45, in build_from_cfg
f'{obj_type} is not in the {registry.name} registry')
KeyError: 'EpochBasedRunnerAmp is not in the runner registry'

Perhaps changing the config to reflect "EpochBasedRunner" instead of "EpochBasedRunnerAmp" may help

This is because you haven't installed this repository's mmdet. You can do that by positioning to its root, and then doing pip install -v -e . . Also, like it was mentioned, you can just remove the Amp part to use mmdet's default EpochBasedRunner


Best way to know which version is currently deployed in production or staging

Usually we merge code to production or staging and we deploy. However it does not always mean that the current production branch is the one that is actually running in production.
Sometimes we need to find out which is the last commit that is running in production/staging. We do write after deloyment to revision.log. Let's look into to see what is the best way for one to find out which commit is running in production/staging and accordingly update how-to.md doc.
@RahulMahale _a please look into it.
//cc @ershad

@neerajdotname for this change, It was pushed here https://github.com/bigbinary/boxy-cap/pull/13
how-to is also updated.
by default we have provision to see the latest deployed commit using
 bundle exec cap innovista-staging deploy:log_revision


[SPARK-5655] Don't chmod700 application files if running in YARN

As per SPARK-5655, recently committed code chmod 700s all application files created on the local fs by a spark executor. This is both unnecessary and broken on YARN, where files created in the nodemanager's working directory are already owned by the user running the job and the 'yarn' group. Group read permission is also needed for the auxiliary shuffle service to be able to read the files, as this is running as the 'yarn' user.

Can one of the admins verify this patch?

Apologies, just seen that I've PR'd this onto branch-1.3 instead of master. Not sure if it can be easily moved.

Closing and re-opening on master as requested.


fixing assembly attributes; improving test stability; incrementing version

Fixes #547

Previous InformationalVersion: 1.4.0-local Commit hash: N/A+dee65e78cbd22ce884dca653f594f0e509c40837
New InformationalVersion: 1.5.0-20210820.11+f21362df7b9444d81ba93f8433d3e6a988c604a5 (the -20210820.11 won't be there for an official build)

I see. I think the change is OK, but we should consider the change to the other projects for consistency (though, that could potentially impact consumers as the host actually uses this information in the status response)


AccessKit integration

Starts work on AccessKit integration (https://github.com/DioxusLabs/blitz/issues/14)

[x] Connect accesskit-winit adapter
[x] Add Dom::visit to traverse the dom top-down
[x] Build initial AccessKit tree
[x] Send tree changes from Dioxus updates to adapter

I think it's best to wait for more interactivity and focus system design before processing AccessKit events with the DOM 🤔   totally open to trying to add that here though

@matthunz Have you tried actually using this with a screenreader?

@matthunz Have you tried actually using this with a screenreader?

Yeah it looks to be reading the elements OK so far, I posted this video in the Dioxus discord a little while back if you missed it
https://github.com/DioxusLabs/blitz/assets/9288430/62c7f072-2d76-46bc-910a-b169b287a631

Hello @matthunz, AccessKit dev here.
I've tried a modified version of the accessibility example to add more kind of nodes and my screen reader is already able to pick them up.
One thing you will have to tackle early on is the labelled_by relationship. I tried an h1 and a button and on both cases the text that my screen reader attaches to the node is the HTML element node. I assume that the actual textual content is a child node of the element, so you will have to put the text node's ID in the labelled_by list property on the parent container.

Hey @DataTriny thanks for your insight!
I switched NodeBuilder::set_name to NodeBuilder::set_html_tag in https://github.com/DioxusLabs/blitz/pull/78/commits/9ae0fb7999b827edccd6a49ed3ed069f1bdc3514 . If there is a plan to send this to the platform eventually I'd say we could keep it here until then :thinking:
I also tried added some basic labelled_by relationships in https://github.com/DioxusLabs/blitz/pull/78/commits/a882185736facb914e9d104ebc372aa39f5984a3 . I'm hoping concatenating child text node ids into the parent elements labelled_by field should give the right result.
I'd also really like to connect to aria-labelled-by at some point :eyes:


feat: improve admin menus and edit screens and adjust permissions

Closes https://github.com/datadryad/dryad-product-roadmap/issues/3343
Closes https://github.com/datadryad/dryad-product-roadmap/issues/3349
Closes https://github.com/datadryad/dryad-product-roadmap/issues/3356

I'm sure I didn't hit every path, but I tested a lot, and everything works fine.


What is a BMP field and how does one set it?

I see the same guidance about BMP fields as here https://support.microsoft.com/en-us/help/291010/requirements-for-domain-controller-certificates-from-a-third-party-ca i can find no instructions on how to modify my windows 2019 CA templates to ensure this.  Please clarify.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c47de28c-e44b-ca73-efde-fae303e0d3f8
Version Independent ID: 71202a24-5b2f-844a-acce-d48c46873f2b
Content: Hybrid Key trust Windows Hello for Business Prerequisites (Windows Hello for Business) - Microsoft 365 Security
Content Source: windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md
Product: w10
Technology: windows
GitHub Login: @mapalko
Microsoft Alias: mapalko

I finally got this install working, i still don't know what a BMP field is - i can only assume a windows server 2019 CA does it? (but i can't see this parameter on the DC KDC cert anywhere)
Also please extend the Key Trust flow documentation to include full certificate instructions  of what the cert on a windows 2019 CA needs to be created (like you have in the Cert Trust flow).

Hello @scyto ,
totally agree, this is pretty confusing,
there is no such thing as "BMP field"
The certificate template must have an extension that has the BMP data value "DomainController" - this means that the template must have an extension with value "DomainController"

BMP just means here that it should be encoded as BMPString
I will create a PR to make it more clear.
Thank you

@scyto  - Thank you for submitting feedback.
From our understanding, the issue has been resolved based on this merged commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/f2f987dc5b4cf49d8d61e52605d6fca3f73439f5.
Thank you for your contribution to make the docs better! Much appreciated!

@mypil This confusing/incorrect wording about 'BMPString' was fixed in that merged commit, but that merged commit is for a different file.  The https://learn.microsoft.com/en-US/troubleshoot/windows-server/windows-security/requirements-domain-controller URL still says 'Basic Metabolic Panel', which is obviously incorrect.


Fixing Bug with KeyCloak Ingress

Fixing Bug with KeyCloak Ingress

It's my bad for not documenting this but it's actually intentional that the service is configured that way. It's a way to ensure keycloak admin console and master realms are not accessible. See this for more information: https://www.keycloak.org/server/configuration-production
I know we are not doing this for production but I do want to follow minimum security measures when exposing things to the internet.

Understood, IMO you can expose it for reference implementation and add notes to say for prod scenarios this is not recommended. I was blind and have to spend some time to fix for my impl. Worst case the paths should be removed vs having wrong port 8081

I see. I should have documented that.
How about we add a switch in Terraform to enable this? Set default not enabled. If users want to have this, they have to change the value themselves. We can put a comment in there and warn users.

Ya thats very fair. I can make that code change sometime and also add comment.


Collection pointer list: improve interface

Depends on #15
Improvements to the PointerList API, so to make it easier to actually create and use a postgres pointer list type from zig code while trying to reduce the risk of using the C API incorrectly.

allows list to be a null pointer. This is how empty lists are represented in postgres
methods that not return a new list but modify the currently allocated list:

accept a pointer value to indicate that the current list is modified
do return void, because the current list is modified and we do not want to give the impression that a new list has been allocated

updated iterator to allow initialization from an empty list (null pointer). No need to check if the list is null anymore.
add some more delete methods

Merged via #18


user_defined_features usage in featurize.py

user_defined_features were previously discarded during data frame standardization in featurize.py.  Featurization with user_defined_features works now.  Fixed the usage of DataFeaturizer.featurize in examples/pdbbind_nnscore.py

TODO: Once I have QuantumMachine deep-chem running I will add a test for user_defined_features feature type

@joegomes Thanks for the fix! Would you like me to merge now (once Travis finishes running) or would you like to add the test before merging in?

@rbharath Either is fine with me assuming Travis is successful.  You could wait since I will have the test added in a day or two

Ack, it looks like the Travis build is failing. Could you look into this locally? You can debug by running nosetests -v deepchem and run the same suite that's running on Travis.
If the test will be added in a day or two, I'll just go ahead and wait for the test (having that in here will make sure we won't break user_specified_features again.

To follow up on this thread, is this fix still needed? Our discussion on Friday IRL suggested that the needed information might have been in the original df to begin with.

@rbharath The original problem this fixed was that the user-defined data was not moved from raw df to the standardized df.  I figured out a better way to do that by moving the add_user_defined_data function into the standardize_df function, so this pull req is a bit outdated.  I'm going to add some commits later today that include this, a few small fixes, and an api test.

I've finished the code for this pull req in a different branch.  I'll close this and submit a new pull req once I get pathos running.


unified priority mapping

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 88.099%

Files with Coverage Reduction
New Missed Lines
%

pkg/listener/send_result.go
1
88.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
4997

Relevant Lines:
5672

💛  - Coveralls