I am writing an ember app, and not using rails nor grunt for anything. I previously had a short python program that took text files and did some markdown stuff with them, and then compiled them all to a templates.js file using ember-precompile:
ember-precompile templates/*.hbs -f templates/templates.js
This worked great until I upgraded ember, and now I'm getting this error.
Uncaught Template was precompiled with an older version of Handlebars than the current runtime.
Please update your precompiler to a newer version (>= 1.0.0) or downgrade your runtime to an older version (== 1.0.0-rc.3).
I need to upgrade my ember-precompile program, but solutions like changing a grunt config or changing gemfiles are no good for me, since I'm not using either of those tools.
Also, attempts to upgrade or reinstall haven't made any changes at all.
Ember version Version: v1.0.0
Last commit: e2ea0cf (2013-08-31 23:47:39 -0700)
Handlebars version Handlebars.VERSION = "1.0.0";
Feel free to fill in any gaps in my understanding. For short term development purposes I'm just going to put my templates in index.html but I want to do markdown stuff to my templates first, so that won't do forever.
You would need to recompile your handlebar files using the latest ember-precompile version that matches the run time version. Basically, ember-precompile that you are using is older version but you are currently running the newer version of ember. That is what the compliant is about.
Turns out I just needed to learn the magic of github and npm and download a non "release" version of the program and install it. Pretty stupid of me really.
If anyone in the future has this problem, just check out npm install and get one of the fixed versions from github in a zip file or whatever suits you.
Related
hopefully everyone will be doing great.
I wanted to ask if the existing version of Qt (not Qt Creator) be upgraded to the latest version? Rather than downloading it separately from Maintenance Tool, and Migrating the Project to the Newer versions manually.
Like, currently I have Qt 6.2.2, and I want to upgrade to Qt 6.2.3 (as, there's a fix I need). To update, I have to download the whole package from the Maintenance Tool, do all the selections all over again, and migrate my existing projects to the newer version.
Is there exist a convenient way? As Visual Studio provides.
The way i do is conan package menager. You have Qt and other great packages there. You can check https://www.qt.io/blog/installing-qt-via-conan-package-manager how to setup or use some existing starter project with it like https://github.com/cpp-best-practices/cpp_starter_project/blob/master/cmake/Conan.cmake#L28 or maybe even https://github.com/conan-io/cmake-conan when you setup your project with conan changing version required you to change for example qt/6.2.2 to qt/6.2.3 and rerun CMake if you using it of course. It will require you to setup conan in your project and that can be tricky. But after that you will see all pros of using conan. Worked great for me.
The documentation explains how to install the newest version, but I need a specific (older) version. Could someone help me with the best way to accomplish that?
The official deb & rpm repositories don't provide the previous Crystal releases. We know we want to improve that at some point in time, but it's not happening yet.
If you're on macOS/using Homebrew, you can try installing a Homebrew formula's old version. There might be a similar procedure in Linuxbrew. And I'm not sure about Arch's situation.
Official Docker images go as far as 0.13, in case that helps.
And you can always install Crystal from a .tar.gz published on the repository's Releases page. Just pick the version you prefer instead of the latest.
Don't forget that, the older the Crystal version, the less supported it'll be.
I'm trying to run yeoman build on a project that uses requireJS and the require-handlebars-plugin. I'm am getting this error when running the rjs task:
<WARN> Error: ENOENT, no such file or directory '/Users/tkrell/Sites/pathrabbit-marionette-require/temp/scripts/template/schedules/day-jobs -past.js'
In module tree:
main
schedules/schedule-layouts
schedules/schedule-jobs-view
hbs
at Object.fs.openSync (fs.js:338:18)
Use --force to continue. </WARN>
I believe this is the same as this issue which appears to simply need the latest version of r.js to be resolved. When I use a newer version of r.js manually, I don't get the error and everything works fine. How can I force the yeoman build task to use the latest version r.js?
The advice given on the issue I created on Yeoman's github page worked for me:
Yeoman uses 2.0.2 (see it's package.json).
You could go into the directory yeoman is installed and run npm install -f requirejs to force install a newer version. No promises it won't break though.
However, in yeoman 1.0 (which is imminent), we'll be using grunt-requirejs instead.
https://bitbucket.org/alfonse/gltut/downloads
this is the repository for the several tutorials in this online-book
http://www.arcsynthesis.org/gltut
the author uses premake as alternative to cmake, and i have tried every possible command line options but nothing works.
I don't get why the author wants to use the latest tool on earth but i need to solve this and i don't even have a clue about Lua and this tool.
For who wants to help me with this you have to download this to actually build the demos and put it in the root folder of your gltut project.
The URL for the mercurial repository is
hg clone https://bitbucket.org/alfonse/gltut
My OS is Ubuntu 12.04 64 bit.
I just noticed that the premake version that comes with Ubuntu 12.04 is the 3.7, just download a newer version from the 4.x branch and the problem is solved.
Last Friday, I've built an RPM spec for my Django project. The RPM creates a virtualenv, downloads dependencies via pip and puts everything into the packages. Today, I've found out that BeautifulSoup 3.2 has been released. Luckily, I've had my BeautifulSoup version pinned in the requirements.txt, so I found out because of the build failing.
Now a completely different matter is: how do I do avoid upgrading stuff in the future? BeautifulSoup has deleted all previous versions from PyPI, so I can't download a version I've actually tested against. pip's download cache doesn't help here either, since pip always tries to check PyPI first.
Can you recommend something to avoid this situation?
First, this is an unusual situation. I've never seen another package remove all old releases the way BeautifulSoup does. I consider that rather user-hostile behavior, except perhaps in cases of a serious security fix.
That said, if you want a reliable build process using pip, you really need to mirror all the packages you rely on locally. It's not hard to do; you can use pip's --download option (or your existing pip cache) to get all the package tarballs, then just dump them in an indexed, web-served directory and use --find-links in your requirements file to point pip there (plus --no-index to tell it not to use PyPI).
The files in question can still be found: just provide the direct url instead of the package name:
http://www.crummy.com/software/BeautifulSoup/download/3.x/3.0.8.tar.gz
for example.