Deployment Completed With Errors

[paul.r.r]

Currently in LV2019. I've only played with LV2020 to mess around with interfaces, and it seemed to crash quite frequently. 

If I get a chance in the next few days I'll look at getting a vm setup with 2020 and the RIO drivers to see if that makes any difference.

[ChrisStrykesAgain]

I've actually had good experiences with 2020. I got in to a weird situation where an interface file (.lvclass) got corrupted repeatedly, but other than that one anomaly it's been pretty stable.

Spoiler

I played with your attached code. It doesn't deploy from 2020 either, or at least not to my Linux RT PXI VM.

[Neil.Pate]

Experienced something very similar this year with a project in LV2020.

Mass compiles for me would crash LabVIEW.

Sadly after several weeks of ridiculous frustration I rolled back to a good commit in git and just recreated the code.

I strongly suspect my problem was due to User Events which my framework uses extensively. My problems always seem to start happening when I do crazy things like rename user events or change the data type of the event data.

I still get the weird deploy error at least once per day which is painful but manageable.

My code had a bunch of classes, but not The AF.

All in all a deeply unpleasant experience.

One thing I found worked some of the time is to rename the first offending class. Then often the deploy works fine.

[Seruhan]

I'm struggling with the same issue these days. Did you find any workaround?

[Hooovahh]

---

@Seruhan wrote:

I'm struggling with the same issue these days. Did you find any workaround?

---

Lots of clearing compile cache, rebuilding, and redeploying on my end, sorry.

[paul.r]

In my case, it turned out that community scoping of classes and methods was a major part of the issue - removing community scoping made it so that I could work around the problem, but I still see the issue. Its just now a series of clear compiled object cache and mass compiling will allow me to deploy, whereas before I couldn't ever get it to run. NI confirmed this was a bug and is apparently working on it, but no real input on the generic issues everyone seems to be facing.

I will say that NI's response here has been quite disappointing - I was graciously helped out by several community members that I am very thankful for, (seriously can't say thanks enough to those of you that reached out to help) but NI didn't do much in the way of providing real help. I discovered the community scoping issue myself through trial and error, and the only solution to the recurring problem not related to community scoping (mass compile/clear compiled object cache procedures) were provided by community members. 

The fact that there is an unknown 'black hole' of problems with NI RT systems is quite concerning for anyone seeking to develop on these platforms - when scoping out a project how can you be sure you won't spend 100 hours debugging an undefined problem with no real support from NI? I found my issue was community scoping, but who knows what the next bug will be and how long it will take you to solve it? 

[Seruhan]

Thanks for the response. Digging forums to find answers for problems that NI never had real support is exhausting. I thought creating project for target from stratch could show what the real error is but what I got in the end is keep deleting caches and recompiling entire folder structure.