I've just downloaded the Kartaview from the above url:
https://github.com/kartaview/openstreetcam.org/
However, I follow the instructions they wrote in the md file.
When I run the server, it throws an error
Apollo module not find.
The url https://github.com/kartaview/openstreetcam.org/ is a link to an existing Kartaview repository. It's a platform we can install it to my local, I followed the instruction in the README.md file. It's just 'ng serve'.
However it throws an error that apollo module doesn't exist. I chased the route it says, there wasn't actually apollo module.
Is this my fault or apollo is somewhat a default module?
Related
I installed the Postman interceptor Chrome extension, the Postman interceptor and the custom Node version I was asked to install and once I try to start the capture I get a toast telling me that there is an "Error creating interceptor session" without any further useful information.
Following the troubleshooting tips I verified that:
Chrome is installed
the directory ~/Library/Application Support/Google/Chrome/NativeMessagingHosts exists.
I have a working internet connection.
my firewall allows Postman to connect to the internet.
I have permissions to read and write in the ~/.postman/InterceptorBridge directory.
I have write permissions to my ~/Downloads folder.
which node yields /usr/local/bin/node
the manifest file com.postman.postmanapp.json is not in ~/.postman but the documentation does not tell where it is even supposed to be. I deleted ~/.postman and reinstalled Postman. The directory did not reappear. The error persisted. I have no possibility to reinstall the interceptor from within Postman now.
Before deleting ~/.postman the Interceptor binary existed therein but is obviously gone now.
Executing pm.interceptorInstaller.reset() in the Postman dev tools did not enable me to reinstall the interceptor either. The error persists.
I appreciate any help.
Postman version: 9.15.8
Chrome version: 100.0.4896.60
macOS version: 12.3
I have a shared Cpanel host with the Litespeed web server. I want to deploy a Django application on it. After creating a Python application inside the Cpanel where I have not deployed the application on the host I try loading the website, and instead of displaying the Django version, I face 503 Unavailable!!
Also inside the "stderr.log" file, there is the following error.
/usr/local/lsws/fcgi-bin/lswsgi_wrapper: line 9: /opt/alt/python39/bin/lswsgi: No such file or directory
I'm creating the application with Python 3.9.
But it works when I create it with Python 3.8 and show the following message when I load the web,
It works!
Python 3.8.6
The issue is mostly caused by the lack of the Python 3.9 WSGI package. On out-of-date versions of LiteSpeed, the package needs to be installed manually.
To work around this, first ensure that LiteSpeed is up to date. LiteSpeed must be at version 5.4.10 for this to work. Once that is confirmed, execute the following script from LiteSpeed. It will pull the required Python Selector packages:
/usr/local/lsws/admin/misc/enable_ruby_python_selector.sh
Refer cpanel support
I am building my ember app in production environment and deploying it on my local wamp server(apache server). But when I copy the file and open the app using url, the handlebar template application.hbs or index.hbs is not rendered.
I am building my project using
ember build --environment production --output-path dist/
But when I open the path 127.0.0.1/path-to-my-project
I get following error in console.
Uncaught Error: Could not find module `ember-data/-private\system\references\record` imported from `ember-data/-private/system/references`
vendor-192d3eef66f0205b64b4acf903f80f63.js:1
I am getting this error when building in production environment,building in development environment is working fine
I checked the documentation and sources available online, but couldn't find the cause for this error.
Please Help...
On Windows, it's mixing / and \s. See:
https://github.com/emberjs/data/pull/4205
If you're using the latest Ember, the solution is to upgrade to Ember-Cli 2.4.2 and use Ember Data 2.4.0.
I'm trying t use the InfoRecoverySample in IS 5.0.0. I was able to build it as according to the instructions here:
https://docs.wso2.com/display/IS500/Recovering+Account+Information+Using+a+Webapp
However after placing the war file in [IS_HOME]/repository/deployment/server/webapps/ and restarting, I get errors in the application logs. Unfortunately they are very vague:
org.apache.axis2.deployment.DeploymentException: Error occurred while deploying webapp : [IS_HOME]/repository/deployment/server/webapps/InfoRecoverySample.war
Error occurred while deploying webapp : [IS_HOME]/repository/deployment/server/webapps/InfoRecoverySample.war
Error while deploying webapp: StandardContext[InfoRecoverySample.war].File[repository/deployment/server/webapps/InfoRecoverySample.war]
My best guess is that the pom.xml file is out of date because I see lots of references to 4.2.0. This is the pom.xml file I'm using:
https://svn.wso2.org/repos/wso2/people/chamathg/samples/is/InfoRecoverySample/pom.xml
Does it sound like I'm on the right track? If so, is there an updated pom.xml file (or sample project) out there?
TIA,
Mike
Deploy the war file in your tomcat/webapps folder, not the identity server webapps. then access via localhost:8080
edit:
The way the pom is designed is for deployment on your localhost, not the wso2 server. Despite what the instructions say. However, you can deploy it to [IS_HOME]/repository/deployment/server/webapps/ as long as you remove most of the jar files that are created in the war's WEB-INF/lib directory. These will conflict when being run from the IS. The only one you need to leave is org.wso2.carbon.identity.sso.agent-1.2.0.jar. remove, re-zip, and then redeploy.
I have been trying to get Gradle working on our Continuous Integration server, which has no access to internet (external) URLs.
Currently, we get our maven-style dependencies from an internal proxy server. So I uploaded the gradle wrapper onto that server too, such that when the CI server starts up it can download the wrapper from the internal maven proxy server.
Problem solved, I thought; the build will carry on and pull down the project dependencies from the internal proxy server as well (it's set up in the build script) and should be OK now.
But in between getting the wrapper Zip file and starting the build, it's doing the following:
Downloading http://maven.internal.mycompany.com:8081/nexus/content/repositories/thirdparty/org/gradle/gradle/1.0-milestone-3/gradle-1.0-milestone-3-bin.zip ................
Unzipping /home/user/.gradle/wrapper/dists/gradle-1.0-milestone-3-bin.zip to /home/user/.gradle/wrapper/dists
Set executable permissions for: /home/user/.gradle/wrapper/dists/gradle-1.0-milestone-3/bin/gradle
Download http://repo1.maven.org/maven2/org/codehaus/groovy/groovy/1.7.3/groovy-1.7.3.pom
Download http://repo1.maven.org/maven2/antlr/antlr/2.7.7/antlr-2.7.7.pom
etc...
*** then the actual build starts ***
Download http://maven.internal.mycompany.com:8081/nexus/content/groups/public/commons-lang/commons-lang/2.6/commons-lang-2.6.jar
E.g. it's trying to pull down extra dependencies for the gradle executable from repo1.maven.org which fails on the continous integration server, as it has no access to this server.
In my build.gradle file I have:
repositories {
mavenRepo urls: "http://maven.internal.mycompany.com:8081/nexus/content/groups/public"
}
and in my ./gradle/wrapper/gradle-wrapper.properties file I have :
distributionUrl=http\://maven.internal.mycompany.com:8081/nexus/content/repositories/thirdparty/org/gradle/gradle/1.0-milestone-3/gradle-1.0-milestone-3-bin.zip
So is there another place I can specify which server the wrapper should use to get it's additional dependencies ? Or is this hard-coded into the wrapper itself ? Or I might be missing a trick here, as Google doesn't seem to show up anyone else having this issue at all !
Ben
Picked up a hint from another forum that led me to the answer - a plugin for cobertura that I was pulling down had it's own gradle build file that included the default maven repositories.
I've removed that now, and the calls to external maven have ceased.