When I go to SpecRunner.html in my browser, the unit tests run fine. The issue I am having is if I change one of the tests, or the code that it tests and refresh the page, it doesn't load the new tests or change at all. I thought that this would be a cache issue, but I have the chrome dev tools disable cache selected.
What am I doing wrong?
Thanks
EDIT: tried restarting my computer, nothing. Clearing cache, nothing. I don't understand why this would be happening.
EDIT2: tried force reload, nothing... changed the file name and reference and still loaded the old code...
This might not answer your specific problem, as there are a million reasons this could happen.
For me, it was because I had deleted some files and then re-added them as a git submodule. After doing this, ls was showing me the OLD files, and I didn't realize that I had to go up a directory and then back in to interact with the new files I had just pulled down.
Old question but I ended up here when looking for an answer, so here's my solution in case it helps anyone - I was having a similar problem with jasmine-rails, removing jasmine-specs.js from public/assets did it for me. I'm using the jasmine-rails gem from https://github.com/searls/jasmine-rails.
Related
This is the second time i'm commenting about this problem and I really hope you can help me this time since i've gained some more information about the problem. So the problem is basically that all my Django projects doesn't update the static files (this also includes projects which I have downloaded). So I can fx still see the old styling from the css files but the changes is not displayed. When i insert the css or js directly into the html file i can see it though. I thought that it maybe had something to do with my browsers stored caches but I have tried to do a hard refresh, clearing all my caches, installing whitenoise and forced browser to reload the css file by adding an extra parameter to the end of the src tag. I have also tried python manage.py collectstatic and almost everything else on this thread.
When the problem bagan to occur I was working with the implementation of stripe. I don't neccessarily think that stripe is the problem since the problem occured hours after i had already implementet the checkout site. I just think it's worth at least mentioning.
Some of my venv packages:
Django | 3.0.3
django-bootstrap4 | 2.2.0
stripe | 2.50.0
Weird behaviour:
Yesterday when I decided to comment out the bootstrap link to see if that was somehow the problem, the changes to the css file got applied to the site. I tried to do that several times and that seemed to be the problem but that only worked for like an hour. Now I cant apply any changes to the sites whatsoever.
My first post:
If you want to see my first post about the problem, you can check it out here. Keep in mind that the problem is not only happening to my Django projects but also the projects which i've downloaded.
I have no idea whats happening and I would very much appreciate your help. If you need any more information please just ask.
Edit:
I created a new folder and css/js file and it kind of worked. I believe the reason it worked was bcs whenever you create a new css/js file, Django needs to atleast load the content of the file once. But whenever I wanted to make other changes it suddenly didn't work again. In my file i had two links to css files. This should usually not be a problem, but apparently it was for me. I deleted one css link and It suddenly worked fine again. If anyone knows why this happened pls tell me, i'm all ears.
Assume you did everything correctly! I once faced this problem too and I fixed it by changed the directory name inside static folder to the same name as my app name. static/css/style.css change to static/app_name/style.css. Also don't forget to refresh the browser (ctrl + r or cmd + r). Hope this would help.
This is already been addressed here but the solution doesn't seem to be working for me.
There's some background here. I've tried many things but nothing seems to be working. Any help would be greatly appreciated!
I ran into the same problem and found that it had something to do with my old mocks setup in server/index.js. I'm not using mocks at the moment so I just deleted the entire server directory and that cleared it up. At some point I'll figure out what was wrong and post an update.
If you have an existing server directory then as of 0.0.46 requests will always get sent there. See: https://github.com/stefanpenner/ember-cli/issues/2089 I had to hack my own version ember-cli to allow it work as expected.
The problem
I'm working on a Lift application for work, managed with sbt 0.11.2. I started working on some javascript files that get served by jetty, and found that they are locked once I run container:start. This is highly annoying because the lock doesn't go away until I completely exit sbt, but I want to be able to edit my files while I see them in the browser.
What I've tried
I googled around for a bit and found some old links like http://www.assembla.com/spaces/liftweb/wiki/Fix_file_locking_problem_with_jettyrun but I couldn't get the solution to work for the 'new' Jetty/SBT (where it's container:run instead of jetty-run). Even more annoying is that the more specific I make my search terms, the less helpful the results become.
Our sbt configuration is done with a build.sbt file, and not the full-fledged build.scala, and I won't be able to change that. I'm hoping that there's some setting that I can add in to stop Jetty from locking my files.
http://wiki.eclipse.org/Jetty/Howto/Deal_with_Locked_Windows_Files
I have a CF9 site set up locally on OSX Snow Leopard, and it's started to behave very strangely - probably about 1 out of every 5 times I load any page in the site, it will throw a 'Cannot find CFML template for custom tag' error. I just refresh the page and then everything works fine. It can happen on any page, but it never happens consistently with any one page. Furthermore, this doesn't happen at all on the live server when the code is checked in through SVN, so I figure it has to be some kind of configuration problem on my local instance. I can still do my work, but it's pretty annoying having to refresh pages ALL the time. Has anyone run into similar difficulties?
Try using <cfmodule template="pathTo/yourTag.cfm"> rather than <cf_yourtag>, so you can specify the exact location of the template (in case the server is getting confused as to where it resides).
FYI, this is based on a tip from Raymond Camden's blog post: http://www.raymondcamden.com/index.cfm/2006/8/17/ColdFusion-Custom-Tag-Tips
Chris, odd that I should run into your question now, as this just started happening to me last night. I have all of my CF errors being emailed to me, and I am seeing that similar problems are happening across multiple sites that all run the same software, some of which haven't been touched in a long time. That got me thinking, it's probably a corrupt compiled template in the CF cache. You can recompile the template by making a slight change to it, say add an extra line or a comment or something, then access the site again. Or, purge the whole cache and let CF rebuild everything, which is likely what I'll do since who knows what else might be affected.
Clearing the Cache in Coldfusion Production server
A while ago, I worked on an application where a manager can approve/deny xxx applications. When some body selects an action from a drop down, it opens a cfwindow and loads cftextarea richtext="yes" in there, so that they could enter reasons for approval/denial.
Now the culprit is that in production, the fckEditor has a ton of funky chars in IE8. Same thing won't happen in FireFox. Also, the IE8 does not show the same stuff in dev.
I have looked at the scripts in /cf_admin/CFIDE/scripts/ajax/FCKeditor, they are all the same.
Since this wasn't an issue before, I am not sure where to look at. Something got updated on the server which probably causes this problem. Does anybody know what could be the problem?
It turns out the vp put the header X-UA-Compatible: IE=IE7 in IIS to force IE8 emulate IE7. When I made them change this to X-UA-Compatible: IE=EmulateIE7, everything started to work perfectly again. For more details see Introducing IE=EmulateIE7.
Hope it helps others. Thanks.