I've spent the better part of today and last night on this and I can't figure it out.
I've searched for a similar error but none of the descriptions seem to fit my case.
My issue is that in visual studio, it's showing that I have uncommitted changes. In this case, it's the deletion of a file.
context: I'm doing a code-along tutorial for Reactjs and I delete my src file and replace it with the tutorial's in case I miss anything and commit along the way. It's been working flawlessly more than half of the way done with the tutorial.
Anyway, now when I try to commit to Github through Visual Studio, I get this error showing,
I've tried revert and reset --hard to before when I got this error and no luck. I don't know what else to do.
Please help.
I somehow got lucky and figured it out.
I just had to delete the existing Aux.js file and it was able to work.
🤷
Related
Had some issues getting an R session going this morning (unusually long loading times, terminated R sessions, etc.) and I've isolated it to one package, QPress that I was trying to load at setup library(QPress
Tried a few times, issue persists, decided to uninstall and reinstall the package install.packages("QPress")
and got a surprising error message.
Warning in install.packages : package ‘QPress’ is not available for this version of R
A version of this package for your version of R might be available elsewhere,
see the ideas at
https://cran.r-project.org/doc/manuals/r-patched/R-admin.html#Installing-packages
Figured, ok, maybe I need to update R. Did that, am now running 4.2.0. Also updated R Studio while I was at it. Still getting the same error message.
Something, somewhere, is messed up and it's over my head. Trying to finish some analysis that I've been working on, without any similar issues, for a while - and can't do squat without this package. More package documentation here on Github, but I could really use a hand if anyone knows where to start here.
An update
I have gotten the package to reinstall, using
options(repos = c(SCAR = "https://scar.r-universe.dev",
CRAN = "https://cloud.r-project.org"))
install.packages("QPress")
Which.. I did try before, but it worked this time. Ok, great, I have no idea where this issue came from in the first place.
Today I came across a bug that I'd like to share with everyone.
When trying to execute an SSIS package in Visual Studio (2015 and 2017 the following can happen (note this package was executed sucessfully before).
While on the bottom it clearly says the SSIS package is finished, the data flow task is still in progress (and will never finish). What also happens (don't know if consistently) a CMD window pops open with "SQLDUMPER.EXE".
This is not due to the way the steps are configured, since executing them individually might still lead to the proper results.
Note as well that in my case this problem makes Visual Studio incredibly unstable. It is not uncommon that after or during every execution Visual Studio crashes completely and is automatically shut down by Windows.
There are no error messages and I had no idea what the reason is this happened untill... (answer below)
After a lot of googling i've found a reason whya multitude of people seem to have this problem.
Right click the project and then click on properties
Click "Debugging"
Set "Run64BitRunTime" to "True"
Apparently for most people this fixes the problem.
For me however I had to come up with another solution.
Right click the project and click on properties
Click "General"
Set "TargetServerVersion" to either the target SQL server and run the package again OR set it to any SQL server version, run the package to see if it works, and if it doesn't set it to another version.
These solutions are counter intuitive because this problem seems to arrise at a random moment and the target sql server version might have been the same throughout the entire development.
I have not tried to see what happens when I deploy the bugged project to a server and see if it runs there, so any and all extra information on this problem would be appreciated.
I spent a good bit of time googling this problem. It looks like it is being reported by many people around the world. It is usually down to either x32/x64 compatibility or some miniscule issue with sorting or data sizes or compiling a custom C# script (or combination thereof).
None of these things worked for me so I rebuilt the entire package from scratch and the issue was gone.
It is far from perfect, especially if your package is large and/or complex but if nothing else works, this is your last resort.
"Run64BitRunTime" was already set to "True", but I was getting this error. so I restarted the visual studio and problem resolved.
None of the proposed solutions worked for me. I had to rebuild both the solution and the project a couple of times and this fixed it. Of course, I opened and closed the VS a couple of times in between. I guess this is a bug and you have to tinker with it to get it to work.
I am experiencing a very strange behaviour of redgate that prevents me from commiting the changes I made to the database (I'm using git). I can click "Get Latest" and get no errors, everything works, but when I try to commit I get an error without any description (please see the screenshot).
I'm asking for help cause I have no idea what maybe wrong. Thanks in advance!
One other suggestion is to create a copy of the GIT config file, (call it GIT2.xml) and add the -verbose switch to see if it then creates some useful output. You'll need to unlink and re-link with the new config file for it to be picked up.
Please make sure that your system's PATH is pointing to the right Git.exe. You may want to check your path for C:\Program Files (x86)\Git\cmd and change that to C:\Program Files (x86)\Git\bin.
I still have no idea what was causing the problem. I ended up committing the changes using Tortoise GIT.
Anyway, no one has spotted that Redgate is performing a git checkout trying to switch a branch into a file?! And surpressing the error with -q. This looks like a bug in redgate.
Maybe the developers misunderstood git's checkout and treated it as subversion's checkout, but this commands are completely different and they should have known it.
Thanks for all the answers.
Here is the post that put some light on my issue:
http://www.red-gate.com/messageboard/viewtopic.php?t=15157
I was working locally on my computer on a cakephp project for 3 days. Then i had to shut off the computer. In the morning, when i turned it on, and tried to continue work, i got error:
Fatal Error (256): ConnectionManager::loadDataSource -
Unable to import DataSource class .DboSource
[CORE/cake/libs/model/connection_manager.php, line 185]
What could be the problem? I haven't changed any of the DB settings. I tried them out with a db manager and they work. I googled this in different ways, but couldn't find the answer.
Any clue would be awesomely appreciated!
Update: I noticed that if i drop the database, or change user/pass to something wrong, this error doesn't change. (..if that helps)
Since the database settings didn't matter, I figured out it was a problem in the system files in cakephp.
So I went ahead and downloaded again the same version 1.3.10 and replaced all over the cake/, plugins/, and vendors/ folders, in which I hadn't changed anything anyway. I only kept my app/ folder.
Finally it's up again.
I suddenly started getting the following error in the "General" ouput window of Visual Studio 2010 when loading the database project as part of a pretty large solution:
Cannot evaluate the item metadata "%(FullPath)". The item metadata "%(FullPath)" cannot be applied to the path "obj\Debug|Any CPU\Database.dbschema". Illegal characters in path. C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
Nothing has changed in the .Net framework recently, and there is not mention of FullPath in the Database.dbproj file.
Googling around yielded this blog entry, but resetting the Visual Studio environment did not help:
http://social.msdn.microsoft.com/Forums/en/vstsdb/thread/14eecc38-87fe-4234-b5fa-c2fa7cab9ae9
After much banging my head against the wall, it occurred to me to try and load the DB project on its own, outside the solution. Lo and behold, that worked. This gave me the clue that something was wrong with the solution itself. I compared the .sln file that was generated when I opened the project on its own with the contents of the large solution, but nothing obvious jumped out. In the end, I deleted the .suo file and that solved it for about a day. The next day, the problem returned, and deleting the .suo file did not fix it.
The culprit? ReSharper 6 EAP. Disable ReSharper and the problem goes away.
http://youtrack.jetbrains.net/issue/RSRP-255109
As a side note for someone that may stumble on this post in the future. Whenever you get a error that says something like:
cannot evaluate the item metadata (fullpath) etc...
Most of the time this relates to the character limitations of paths that cannot exceed 260 characters all the way to the bin folder. It is a really cryptic error that has wasted too many people's time in the past.
Watch the length of those project names and the depth of your folder structure ;-)