In my project, http://lacinia.readthedocs.io/en/latest/, the downloads (PDF, epub, single-page HTML) doesn't update on a build. It looks like it builds, but the download link keeps downloading a version from Oct 03. I've done some significant work since then.
The latest link works correctly, showing changes within minutes of my pushing changes.
It's not clear to me whether the build works, but the latest files are simply not put in the correct folder for download, or if the build is broken in some way.
I'd appreciate any clues on how to fix or at least properly diagnose this.
Digging around, I found the "wipe build" functionality; that plus, perhaps, a Cmd-Shift-R, to ensure I was downloading fresh and not from local cache, got me the latest versions.
Related
I get this error some 23 times when publishing the website. There are no issues with compilation and testing. I know someone is going to have the urge to say "remove the duplicate reference from the web.config" but that's not the problem here. This is a project started in 2008 and the use of ReportViewer predates the code being added to our git repository (which in turn predated me working on it) so I know that nothing is technically wrong with the code. In fact, until last week, it published just fine. What changed? I finally got a newer, faster computer. The client wanted one line removed. I put the code on the new computer, removed the offending line, built, tested. All is ok. Then I went to publish and got the ReportViewer error. I'm working with a byte-for-byte copy of the project on the old computer and the only thing that fails is the publish on the new computer.
Clearly something isn't installed on the new computer that's preventing publish, but I don't have a clue what it is. (Or possibly something installed that shouldn't be. The "new" computer was actually in-use by another developer.)
I was grasping at anything for this problem. I got the idea to remove all copies of the ReportViewer DLL from the Microsoft.ReportViewer.WebForms folder. There were 5 different versions. Windows itself balked when I tried to move version 10. That was my clue. It turns out that whoever switched from version 10 to version 12 missed a couple of source files. I updated the reference to version 12 and the problems cleared up.
Now the real mystery is: why did it ever work on the old computer?
I'm trying to set up a blog via Jekyll and GitHub Pages. To deploy it was not such a big deal, however, in trying to follow the steps described here I only managed to make it display the dark skin locally. Is there a way to deploy it on GithubPages as well?
I installed it via
gem "minima", git: "https://github.com/jekyll/minima"
then added the following two lines in _config.yml
minima:
skin: dark
This is the repo holding the ruby code.
i had this problem too. I learned that the software used by github pages isn’t updated often, hopefully for stability reasoning. You can check what versions they use at https://pages.github.com/versions/. The newer version of minima has the alternative “skins” sass/css feature, but the one currently on github pages doesn’t—-heck, github pages still hasn’t updated Jekyll to v4!!... You should be able to see the build error by clicking Actions on the github repo, then clicking on the last “workflow”, then click on the red-colored build. It’ll say the key in the config file doesn’t exist or somethin’ like that, on the skin: dark line.
anyway, in the config file, add remote_theme: jekyll/minima to force download the latest version from the github repo upon rebuild. Don’t use ~jekyll-theme: minima (or whatever it’s called). In fact, at the moment, all of the themes that come pre-installed with github pages are quite old now...
but really though, use the jekyll discussion site https://talk.jekyllrb.com/.
I was using Chrome, and apparently the Clear browsing data in the last hour with Cookies and other site data and Cached images and files checked made the local updates appear live.
You can go even further and make your jekyll/minima powered site respect users theme preference
https://alexander-taran.github.io/2022/06/08/adopting-dark-theme-in-jekyll-blog.html
please help my umbraco site when i try to login to backend comes up Server Error in '/' Application i attached a screen grab below.
I believe this is due to a conflict with something in your binary folder. All the searching I did on this error revealed a common link to a conflict with certain versions of Umbraco VS Contour.
The most common suggestion is to rename the Umbraco.Forms.Core.Providers.V7.dll file in your bin directory.
If this works, you need to look into which version of Contour you should be using for the version of Umbraco you have to see if there is a conflict there.
If that doesn't work, you might want to look at whichever packages you've installed lately and start removing their DLLs.
Worse comes to worse, rename your bin folder, bring in a fresh one for the version of Umbraco you're using, and then bring the DLLs from your renamed bin folder until you can narrow down which one it is that's causing your grief.
I hope that helps!
I have made some codes in a newer version of my library through Google Scripts. However, I want to revert back to a previous version of the library and make edits of that.
For example: I have 24 versions and want to go back to version 16 for editing, how do I do that without deleting version 17 to 24. The newer versions were used for tests and some of the codes do not work as much as I want to but I want to still keep it to debug.
Thanks for any possible solutions!
Using timestamp information, you can select the Revision that corresponds to the Version you want to restore for editing.
Explanation
There are two mechanisms used for version management in Google Apps Script, both accessible under the "File" menu.
Revision History - this is equivalent to an "auto-save" feature in a text editor. Revisions are saved frequently, and timestamped. There is a facility to select past revisions and restore them.
Manage Versions - to support library development (your case) and script publication, you can create numbered versions of your script. While you can select specific versions to publish or include as a library, and delete saved versions, there is no facility that supports reversion of the most current script content to a previous version.
Example
This example illustrates the idea. Normally, your Versions would be much further apart in time than in this example.
The file Revision history doesn't correspond to a project Version. In Mogsdad's example, how do we know the 38:34 time wasn't where we saved v1?
I typically get in the habit of saving a new copy of the entire script file right after saving a new version, then copying and pasting code from old files that were renamed to the version I saved them at over the working file if I ever need to revert back to the exact way the code was at the time of a past version. Guess there could be a restore-code-to-saved-version option that would make the whole process better.
There was also just a demo done today that could be useful in working with your own version control.
I have a weird problem in an windows phone 8 project (Visual Studio Express for windows phone 8) that Changes to xaml( ex:change visibility of control) don't reflect on App until I rebuild the project and deploy it again to emulator or device.
The changes reflect normally in the design window of visual studio but didn't reflect on the running App.
I did many researches and they didn't help, like:
1- Change "Build and Run" to "always build" when projects are out of date.
2- I checked configuration manager as This post suggests but it was selected.
I have the exact same issue. I have a work around at the moment to save the hassle of rebuilding the solution because rebuilding deletes and re-installs the app and changes any saved settings you've made while debugging. The work around is to switch between configurations. So I'll execute the app in Debug, make some changes, then the next time I execute I change config to Release, and the changes are there.
The difference I can see is when it works I can see the Build Output line which says "Updating the application as the manifest file has changed..." take a few moments to complete. When this issue occurs the output line appears for a split second and so you can tell the incremental deployment hasn't actually been deployed to the device/emulator.
This is a little frustrating so hopefully someone has a real answer. I have other projects on the same machine and they don't have this issue. Just the one project so I don't think its a VS2012 problem.
I've also tried suggestions from other sites saying delete bin and obj folders but that didn't work.
I had the same issue for some of my WP8 Silverlight projects in VS 2013. I couldn't understand why it happened only for some projects but not all, but eventually I found this forum thread. The solution is the following: if the name of your app includes spaces, you definitely need to remove them or replace say with the underscore char. This recipe helped to recover my 'problem' projects.
I also noticed that numbers at the beginning of app name cause the same problem. I solved it by removing numbers from solution and app name.