I've got an issue with the CubeIDE from STM (Version 1.1.0).
I generated a Cube project, worked with it for 2 months, edited it,... no major problems. But suddenly the IDE deletes files like my main.cpp,..
I just did some adjustments, like adding another AD-Channel and generated the .ioc file with the MX-Editor.
Luckly I've got a backup on Bitbucket but I cannot work on ths project because I really need the adjustments I've done.
Is this a bug or am I too stupid to do some adjustments without deleting needed files?
Has anybody this problem too? Or a solution? I would be really thankful.
Related
Overnight, any help I had for Unity3D in VSCode, i.e. intellisense, disappeared. And I get the sense, no pun intended, that I'm not the only one who's afflicted.
I've tried updating and reinstalling what I assumed VSCode needed to make Unity3D intellisense work. And have checked and re-checked settings, reinstalled VSCode package, in Unity3D.
I've worked through a few tutorials that claimed to address the issue.
What else does VSCode depend on to make this relationship work?
Thanks! Here's to hoping you've fixed this and your life has gotten easier!
Try going to Edit > Preferences > External Tools > Regenerate Project Files (This is because of a bug where the VS Code extension doesn't generate the project files correctly the first time, you can check it out here).
You'll need to be using the VS Code Editor Extension 1.2.0 (you can check which version you're using in the package manager) or later for that option to appear. Also if for whatever reason there are 2 .sln files in your project folder (I've had that happen before, though it's less likely), that also causes problems.
Ok. First, thanks to Lightning_A and Charleh!
The resolution to my specific circumstance was to install the VSCode extension "Unity Snippets Modified" https://github.com/with-heart/vscode-unity-snippets
I had been using https://github.com/kleber-swf/vscode-unity-code-snippets.
Perhaps it's just a matter of Kleber's extension, which is/was great, was broken upon updating Unity to 2020? I dunno and don't have the time to look into it, unfortunately.
Hopefully, my question, the answers I received, and my subsequent resolution saves others from the rabbit-hole I went down.
Again, thanks everyone!
I've been using the ESM module with VSCode and my Mocha unit tests for a long time now, a couple of years at least. Recently when I launch an individual test file in VSCode and set a breakpoint in the test file, it no longer breaks in the original file, but rather breaks in the "ESM compiled" file. I don't really know how ESM works enough to talk about it very well, but the file is compiled/transpiled/transformed in some way with all the imports converted to non-ESModule code. I'm able to step through, and it continues to step through other files as well, but each new file opened is this newly "ESM compiled" version instead of the original file, like it used to be. I only just noticed this recently. So I decided to install and older version of VSCode and see if it still happened, and it turns out it doesn't. With version 1.45.x it works as usual, but with anything newer, I get all these "ESM compiled" files opening up when I step through code.
Does anyone know why this is happening? Is there any new setting I can set in the newer VSCode versions that would cause this to not happen? It's really more of an annoyance than anything. I can still get my work done, but it's not as streamlined as it used to be. I will probably end up just downgrading permanently until I can find a way to make it not occur in the new version.
So, if anyone has experienced this, or knows of something new in VSCode that would cause this, I'd really appreciate some help. Thanks.
I'm an Business Intelligence Developer. I'm developing for/maintaining a Microsoft BI Solution at our Company (SSIS,SSAS etc.). Recently I updated my Visual Studio to 2019 Enterprise (before that I was on 2015 Enterprise). Integration Services Extension Version 3.4. (also tested 3.2). With VS2015 everything was fine..
Part of our Data Warehouse is data coming from an PostgreSQL DB. I'm connecting to this using the official Postgres ODBC-Driver (32Bit, Unicode). I tried version 10.01 (old one, worked with VS15 without issues) and 12.01 (current one).
The Issue is the following: I opened the package I have the issues with. It warns me that the PSQL-ODBC-Datasource needs new metadata (nothing changed there nonetheless..). I can run the (unchanged) Package without any issues! Then I double-click the Source. A dialog pops up if I want to correct the Metadata of the Source according to the db it points to. Then the warning disappears. But If I run the package now it fails instantly telling me that the Source I just updated needs new Metadata.
I tracked the issue down to a minimal example. If I get data from a timestamp-column on the PSQL-ODBC-Datasource I allways get, immediately after execution of the package, an VS_NEEDSNEWMETADATA-Error in Visual Studio (SSIS) and the package won't run. There is no yellow Exclamation-Mark on the Source like it is usual. Everything seems fine on design time. I can even preview the output of the source in it's properties. If I select another column instead of the timestamp-column there is no issue. If I select the timestamp-column again it again gives the error on runtime. I also tried different Postgres servers with different versions as Source and different ODBC-Drivers.
If I set ValidateExternalMetadat to False on the source everything is running fine, but this can't be the solution as it worked flawlessly previous.
It seems like SSIS-Packages created with Visual Studio 2019 can't retrieve timestamp-columns from PSQL-ODBC-Sources if ValidateExternalMetadata is enabled.. This is driving me nuts!
Did anyone have this issue and find a solution?
Greetings
Edit: Further Investigation: It seems like VS2019 translates a PostgreSQL Timestamp now to dbTimeStamp2 instead of dbTimeStamp (like 2015 did) on the Output-Columns. But the Metadata also stored in the Package-Xml seems like it's telling that the columns are dbTimeStamp. This mismatch seems to be the Core-Issue why the Package is telling the the Metadata needs to be updated!?
OK I ran into the same problem here and it drove me crazy. I have the same setup and I got the exact same error messages.
Unfortunately I have no solution for this problem but at least I can tell you that it doesn't seem to be a isolated issue as I'm affected as well.
I overcame the problem for the time being by disabeling ValidateExternalMetadata but thats not a setup for production environments.
Thanks for this post though. I helped me not to feel like an idiot again. :D
Cheers
Daniel
Be careful with the casing. I had a view (as data source) in development, with two columns in uppercase.
Before creating the view in production, I decided to change to lowercase both columns, just because all was in lowercase and that two columns were the only things in uppercase. Then I created the view.
My ETL ran fine in DEV, but it didn't in PROD. Finally, I realized that the difference in casing was the problem.
When I changed the view in PROD, so that it was the same as in DEV, it worked smoothly.
Just to get some context here is a screenshot, though you probably gathered this from the title:
Xcode is marking all symbols as undeclared, usually this would be because it doesn't exist or isn't imported, but in this case it was working fine 20 minutes ago and weirdly the project compiles and runs with no problems.
When I compile the errors go away but there is no syntax highlighting, as soon as I start to edit the file the errors all come back. I can work if I remember the exact signatures for anything that I need to use but with the lack of code completion and errors this is very hard.
Notably this is only a problem in a few source files, its not even the whole project. Nothing has changed that I am aware of that could cause this.
Before anyone suggests it, I have tried cleaning, deleting derived data/build folder, restarting Xcode etc...
My colleague is seeing the exact same issue on his machine.
So I managed to fix the offending source files, I just compared their attributes to those of a working source file and it turns out that the problem files included the tests project in their target membership and the working file did not. I'm not sure why this is causing the issue as other projects use automated testing without a problem. Nonetheless this solved it for me, at least until I start writing test cases...
When I update my local working copy of an SVN repository in Eclipse using the Subversive plugin it isnt bringing any new files which have been added to the SVN repository. It thinks that the local working copy is up to date and if I ask Eclipse to update it it just says no further changes.
Anyone got any ideas why this is happening?
I just discovered this nasty problem too. It might be related to this bug report.
Deleting the entire tree worked for me too, but that hardly seems like a satisfactory solution. What scares me more is wondering how I will notice that a certain file didn't get updated, if this happens again.
Thanks to the above bug report, this worked for me (eclipse 3.7):
Team/Update to Version...
v Update to HEAD revision (=default)
Depth: Full recursive (default is Working copy)
v Change working copy to specified depth (default is un-checked)
O Ignore externals (=default)
v Allow unversioned obstructs (=default)
I do not know if that fixes the problem permanently. At least it seems a faster solution rather than full checkout.
Sorry I don't have a solution to this problem, but I have it as well, and I don't have enough cred to comment.
Here is a thread describing the same issue:
http://www.eclipse.org/forums/index.php?t=msg&th=14710&start=0&
A "workaround" I found to be successful is deleting the relevant tree (of course, backing it up first) and performing an "update". I am prompted to recreate missing files, which bring the un-added files from the repo as well. Obviously this is a terrible solution, but it does work.
Another interesting effect to note is that it is one-sided. The other machine on the repo is perfectly fine with updating new files.
I have noticed Subversive to be a bit problematic. While this isn't a direct solution to your problem, may I recommend using TortoiseSVN (assuming you're in Windows). It works excellently, has more power than Subversive, and is integrated with your shell making it a smooth transition.