I have two web apps running on OpenShift Pro, they have been running nicely for a couple of weeks but today I had to make a very small change and push the change to OpenShift. The push failed...
Upon investigation I have discovered that both apps have the same problem (which is strange).
The problem:-
On the Builds | AppName page there is a button labelled Start Build. Clicking this button just produces an error message alert:-
An error occurred while starting the build. Reason: Error resolving
ImageStreamTag jboss-webserver30-tomcat8-openshift:1.2 in namespace
openshift: unable to find latest tagged image
If I click on the latest build I go to the Builds | AppName | Build # page where there is a button labelled Rebuild. Clicking this button rebuilds successfully.
The real problem here is that this means that GitHub pushes fail to start a build, so development and changes are no longer possible...
Any ideas as to why Start Build no longer works?
I think it may be a problem at OpenShift as I have changed nothing recently...
Looking into what happened but you can update your build configuration to use tag 1.3 or latest instead of 1.2.
Related
I am new to Clojure and not a pro in Javascript. I am watching the free part of the course on Reagent.
Following the instructions on the course's repo, after doing the git clone and the npm install, the author indicates running $ npm run dev. Everything seems to work fine. I can see the app on my http://localhost:3000/.
The favicon with the app's logo and its name is loaded on the corner of the browser's tab:
However, on the bottom of the web page, there is this error message from shadow-cljs:
shadow-cljs - Stale Output! Your loaded JS was not produced by the
running shadow-cljs instance. Is the watch for this build running?
Why is this happening? How should I fix it?
How to guarantee that the watch for this building is running?
Is there a simple command to run on terminal to check this?
Obs. 1: If this is relevant, my operational system is NixOS and this is my config file.
Obs. 2: I am not sure if this question is connected to my previous question on npm and Cider (Emacs IDE for Clojure) that happened while working with this same repo.
It is likely that this is due to you running npm run dev AND cider-jack-in.
I don't use emacs, so I'm not exactly sure what cider-jack-in does, but I believe it launches a new JVM. Since the npm run dev also did that you end up with two running JVMs, which also means two running shadow-cljs instances. That is not ideal and they will start interfering with each other leading to errors such as yours.
So, either you run npm run dev and use emacs to connect to that server. cider-connect or whatever is called should do that.
Or you don't run npm run dev at all and instead only cider-jack-in and then start the watch from the REPL.
Don't forget to first kill all java processes that might be running for that project. As long as there is more than one shadow-cljs process running for the project things will be weird.
This happens to me when I clicked on the build link BEFORE it has compiled. In which case, the link is displaying a previously compiled version, not the live version, and "watch" on code changes doesn't work either. Just wait for your terminal output to say "compiled" before clicking on the link.
I have read the posts similar to this but to no avail.
I am in the midst of a comprehensive tutorial for Angular (5). I am on MacOs High Sierra 10.13.3. I am using Chrome Version 64.0.3282.140 (Official Build) (64-bit).
I just completed one project in the tutorial. I am now trying to complete the next project in the tutorial. The project is set to use the default port 4200 on localhost. All of the projects have executed this way.
I have performed my npm install. My npm start script is simple, = "ng serve". I enter npm start and it serves up the project as expected. I then go to my browser and enter the address localhost:4200. The previous project renders. I can't get the current project to render. These are the things I have tried to remedy the situation:
sudo lsof -i tcp:4200
changing the start script to ng serve --port 4300 and then using the address localhost:4300 (tried it with 5000 too)
Actually the first thing I did was look for an active activity on port 4200 in the Activity Monitor
Clear my Chrome browsing history
Restart my computer.
Tried the same process using Firefox as a browser
Tried it using Brave as a browser
In each and every case when I enter localhost:(anything) I get the previous project. Any ideas?
If I could delete this question I would. I discovered the problem.
I only THOUGHT I was pointing to the new project. In reality, I was pointing at the old project. THAT is why the same thing kept coming up and that is why nothing I tried would work.
I am embarrassed. Clearly, I am still a rookie. I hope no one spent any time on this.
Out of the blue recently, I started receiving notifications that my Jekyll builds were failing on GitHub Pages:
Page build failed. For more information, see https://help.github.com/articles/troubleshooting-github-pages-builds/.
Besides that, there was no info given, and the site built fine on my local machine. I tried everything I could think of: I built the site locally (worked fine on my machine), I deleted the last few files that had been added (no improvement), and I reset the master branch to exactly as it was when I last had a successful build. I figured for sure the last tactic would work, but I kept getting build failures.
I eventually figured out the answer, which I'm going to write in a moment.
It turned out the problem was that GitHub upgraded their version of Jekyll. I had to come to the solution by two steps:
Upgrade the github-pages gem on my own computer:
$ bundle update github-pages
Discover an interesting new error message:
Liquid Exception: undefined method `gsub' for 1000:Fixnum in /_layouts/post.html
After some fiddling around (and using Jekyll's --verbose option to find where the build was choking), I discovered that this gsub error was caused by a post I had, which was titled "1,000". (It was about a sleepless night, where I tried to count my way to sleep, and gave up after 1,000.) Some updated parser was trying to parse this as a number, apparently. To fix it I changed
title: 1,000
to
title: "1,000"
And voilà, GitHub Pages was satisfied.
I just installed and repaired my VS2013 to build Native Cordova App. I have also installed the latest version of NodeJS but whenever I am trying to build the Application It gives me an error. I am uploading an image for more details on error as I believe image provide more info than text.
Posting error details if error is not clear in an image
Cannot find module 'q'.
The command ""C:\Users\nnnc\AppData\Roaming\npm\node_modules\vs-mda\vs-cli" prepare --platform Android --configuration Debug --projectDir . --projectName "BlankCordovaApp1" --language "en-US"" exited with code 8. C:\Users\nnnc\AppData\Roaming\npm\node_modules\vs-mda-targets\Microsoft.MDA.targets
I have advanced a little bit more but having hard time to run the application I have to manually installed all the required module. but now whenever I am running my project I get an error of web page is not available. please look at the attached image again.
I found that running npm install from within /vs-mda/ solved all my problems.
found the fix and that Involved manually loading packages like q via node js and in the end the fix for web page is not available was that ripple has changed and now we should not add it as an extension via chrome. it should be done via node js as well as below
npm install ripple -g
but before doing that delete it from chrome if you have got it otherwise just run the command.
Regards
Don't know what happened, but it just hangs on "Type Space loading (4%)" and that's it. I tried to solve problem with -clean option and with deleting .history and eclipse resources folder under plugins. I also tried with new workspace and it's still the same.
Before that I installed JVET. Don't know if it's connected with that.
Yes, it's because of VJET, see https://www.ebayopensource.org/jira/browse/VJET-57
To me it happened on a fresh installation of Eclipse IDE for JavaScript Web Developers.
Just leave it for about half an hour and it should finish successfully.
May i ask why did you install VJET? If as me to be able to debug node.js you might wanna try https://github.com/joyent/node/wiki/Using-Eclipse-as-Node-Applications-Debugger