MdlSelect - ViewDestroyedError: Attempt to use a destroyed view: detectChanges - angular2-mdl

I'm getting the same issue as mentioned in this
github issue
I'm using the following versions:
"#angular-mdl/core": "^8.0.0",
"#angular-mdl/popover": "^8.0.0",
"#angular-mdl/select": "^8.0.0",
From the issue, it seems that this was fixed in this PR and was published as #angular-mdl/select:0.11.2, but I don't see that fix in version 8.
Could you please help me out with a fix for this issue on "#angular-mdl/select": "^8.0.0"
Thanks in advance.

Related

What's the normal procedure for finding the name of the necessary ESLint package based on the config name given in the error message?

I was just struggling with the error below in my IDE for a frustratingly-long time:
ESLint: Error: Failed to load config "#vue/typescript" to extend from.
After a lot of Googling and running commands I found online, I eventually found that what (seemed to) fix the problem was running this:
yarn add -D #vue/eslint-config-typescript
My question is: How was I supposed to figure that out? Is there some website or service or something where I could have searched for #vue/typescript and found out that the package I needed to install was #vue/eslint-config-typescript?
Ok, I figured it out: in the ESLint docs, it says that basically that the part after the forward-slash should be understood to always start with eslint-plugin:
They show the following examples:
"plugins": [
"jquery", // means eslint-plugin-jquery
"#jquery/jquery", // means #jquery/eslint-plugin-jquery
"#foobar" // means #foobar/eslint-plugin
]

Could not find org.nodejs:node

I am trying to build my gui application (angular implementation) and I am getting the following error:
Caused by: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find
org.nodejs:node:10.14.1.
Searched in the following locations:
- https://nodejs.org/dist/v10.14.1/ivy.xml
build.gradle contains (relevant to nodejs):
node {
version = '10.14.1'
npmVersion = '6.4.1'
download = false
}
dependencies {
classpath("com.moowork.gradle:gradle-node-plugin:1.2.0")
}
}
apply plugin: 'java'
apply plugin: 'com.moowork.node'
gradle.properties contains:
systemProp.https.proxyUser=''
systemProp.https.proxyPassword=''
systemProp.http.proxyUser=''
systemProp.http.proxyPassword=''
systemProp.https.proxyHost=internet.proxy.company.com
systemProp.https.proxyPort=port
systemProp.http.proxyHost=internet.proxy.company.com
systemProp.http.proxyPort=port
npm config contains:
https-proxy=http://internet.proxy.company.com:port/
proxy=http://internet.proxy.company.com:port/
registry=http://registry.npmjs.org/
sslVerify=false
strict-ssl=false
Even if I remove the node js dependency (for giggles), it still throws this error. Any help is greatly appreciated. At first, I thought it was a proxy issue but I do not think that is the case. Any ideas?
com.moowork.node is not actively maintained and has this issue. Switch to the fork of this plugin which is actively maintained and has fixed this issue.
https://github.com/node-gradle/gradle-node-plugin/
For more details as to why it is failing, see this comment.

'.' is not recognized as an internal or external command - wdio

When I try to run the code ./node_modules/.bin/wdio config
I have got this error:
'.' is not recognized as an internal or external command, operable
program or batch file.
Package.json
"#wdio/cli": "^6.1.22",
"#wdio/local-runner": "^6.1.22",
"#wdio/mocha-framework": "^6.1.19",
"#wdio/spec-reporter": "^6.1.14",
"#wdio/sync": "^6.1.14",
"chai": "^4.2.0",
"chai-webdriverio": "^1.0.0",
"chromedriver": "^83.0.0",
"local-runner": "^0.1.1-alpha",
"wdio-chromedriver-service": "^6.0.3",
"webdriverio": "^6.1.11"
Could you please help me?
The dot slash annotation is not working on Windows, as where you can just leave that part out.
Linux / MacOS
./node_modules/.bin/wdio config
Windows
node_modules/.bin/wdio config
Though, if you wanted to, you could use .\ and it would work.
.\node_modules.bin\wdio config
The explination here is the difference between the directory separators along with the path.
. = current directory
.. = parent directory
./ Mac, Linux, etc
.\ Windows, Windows 2000, etc

Symfony2: Unrecognized options "method_access_control" under "jms_security_extra" error

So I'm trying to configure security access for some of my methods here, through JMSSecurityExtraBundle. I simply followed the instructions here : JMSSecurityBundle Doc.
I ended up having this in my config.yml file:
jms_security_extra:
secure_controllers: true
secure_all_services: false
method_access_control:
'MyBundle:.*:postEntityDelete': 'hasRole("ROLE_SUPER_ADMIN")'
Now I'm simply getting that error:
InvalidConfigurationException: Unrecognized options "method_access_control" under "jms_security_extra"
How can I have gone wrong on so little? Where's the catch and how do I solve this problem?
Thanks in advance!
Edit:
Deps :
[JMSSecurityExtraBundle]
git=https://github.com/schmittjoh/JMSSecurityExtraBundle.git
target=/bundles/JMS/SecurityExtraBundle
[metadata]
git=https://github.com/schmittjoh/metadata.git
version=1.1.0 ; <- make sure to get 1.1, not 1.0
[JMSAopBundle]
git=https://github.com/schmittjoh/JMSAopBundle.git
target=/bundles/JMS/AopBundle
[cg-library]
git=https://github.com/schmittjoh/cg-library.git
[JMSDiExtraBundle]
git=https://github.com/schmittjoh/JMSDiExtraBundle.git
target=/bundles/JMS/DiExtraBundle
Deps.lock:
symfony v2.0.13
twig v1.7.0
monolog 1.0.2
doctrine-common 2.1.4
doctrine-dbal 2.1.6
doctrine 2.1.6
swiftmailer v4.1.7
assetic v1.0.3
twig-extensions 446d870272cd87a720e95242eade38a2acf56eaa
metadata 1.0.0
SensioFrameworkExtraBundle cb61b92ed55241d93ed9726bc3f5f47c7d2ce8fe
JMSSecurityExtraBundle e752f888c51425f71382c056961f10f2be642102
SensioDistributionBundle 20b66a408084ad8752f98e50f10533f5245310bf
SensioGeneratorBundle b1ccb78c1743f30817b0fce9bb5c6baff6ed7bf8
AsseticBundle v1.0.1
What version of symfony and of the bundle are you using? The documentation you linked is following the master branch. There are links in the upper left to change versions. 1.0 doesn't seem to have that configuration option.
the deps file should contain:
[JMSSecurityExtraBundle]
git=http://github.com/schmittjoh/JMSSecurityExtraBundle.git
target=/bundles/JMS/SecurityExtraBundle
version=origin/master
You can also see here for someone else that had the same issue https://github.com/schmittjoh/JMSSecurityExtraBundle/issues/24

CruiseControl.Net CCNetWorkingDirectory parameter problem

I'm working with the latest CruiseControl.Net 1.5.7256.1.
I'm trying to use one of the system parameters, CCNetWorkingDirectory under sourcecontrol block and the project failed to recognize this parameter.
<sourcecontrol type="svn">
<trunkUrl>https://padev/svn/physical/Source</trunkUrl>
<workingDirectory>$[CCNetWorkingDirectory]\SVN\Source</workingDirectory>
<username>ccnet</username>
<password>hidden</password>
</sourcecontrol>
I also tried it as $CCNetWorkingDirectory, $(CCNetWorkingDirectory), Non of these option worked.
Thank you
You got trapped. I think almost anybody who starts with CCNET tries to access CCNetWorkingDirectory inside CCNET configuration. This is not possible. Find my answer on a similar question here.
I don't know in which version things changed but as of version 1.8 you can use what they call: System Paremeters as documented here:
http://confluence.public.thoughtworks.org/display/CCNET/Dynamic+Parameters
and it works for me as in this sample configuration:
<project name="ProjectName" queue="myqueue" queuePriority="1">
<workingDirectory>path</workingDirectory>
...
<sourcecontrol type="svn">
<workingDirectory>$[$CCNetWorkingDirectory]</workingDirectory>
...
</sourcecontrol>

Resources