hooovahh Posted June 6, 2017 Report Share Posted June 6, 2017 Update: this issue has been fixed in VIPM 2017f1 I've been using the new VIMs feature of VIPM 2017 and am having some issues getting it to build successfully. If I have a VIM on the palette it builds just fine, but if I add a VI that calls that VIM the build fails, even if that VI isn't on the palette. Attached is a zip with my source. It fails to build because the normal VI "Is Variant Repository.vi" calls a VIM that is in that package. If I delete that VI the build works fine. Is this a known limitation that a package can't be built, if a VI calls a VIM? Here are the errors seen when the build fails. Thanks. Variant Repository Source 2017.zip Quote Link to comment Share on other sites More sharing options...
hooovahh Posted June 21, 2017 Author Report Share Posted June 21, 2017 So...is anyone from JKI monitoring these forums? I have a show stopping bug that I posted two weeks ago, in the latest version of VIPM, can anyone give any advice? Thanks. Quote Link to comment Share on other sites More sharing options...
drjdpowell Posted July 14, 2017 Report Share Posted July 14, 2017 (edited) I have the exact same issue: At the moment, I'm only calling VIMs inside my Examples, and so I'm excluding Examples from the package temporarily. Edited July 14, 2017 by drjdpowell Quote Link to comment Share on other sites More sharing options...
drjdpowell Posted July 14, 2017 Report Share Posted July 14, 2017 Interestingly, I have a couple of VIMs that contain other VIMs, and they don't produce this error. Only the VIs that call VIMs do. Quote Link to comment Share on other sites More sharing options...
hooovahh Posted July 18, 2017 Author Report Share Posted July 18, 2017 Interestingly, I have a couple of VIMs that contain other VIMs, and they don't produce this error. Only the VIs that call VIMs do. This is what I observed too. Quote Link to comment Share on other sites More sharing options...
Ashish Posted August 9, 2017 Report Share Posted August 9, 2017 Hi !! Apologies for missing out on these. We were able to reproduce the behaviour and have recorded as Case 17570 for VIPM team to take a look at. I will get back to you when there are more updates on this. Quote Link to comment Share on other sites More sharing options...
hooovahh Posted October 6, 2017 Author Report Share Posted October 6, 2017 (edited) The recently posted update VIPM 2017 F1 fixes this issue for me. Finally I can build all the VIM packages I've been wanting to. Edited October 6, 2017 by hooovahh Quote Link to comment Share on other sites More sharing options...
Ashish Posted October 13, 2017 Report Share Posted October 13, 2017 Great! It was indeed one of the fixes implemented in VIPM 2017 SP1. Thanks for confirmation and glad to know that you were able to build the package successfully. Quote Link to comment Share on other sites More sharing options...
TomMcQ Posted December 7, 2018 Report Share Posted December 7, 2018 Sorry to open this thread again. However, I have VIPM 2018.0.0f1 and I am trying to build a package with VIMs in and I am getting exactly the same issue that James Powell posted earlier in this thread. Please can you tell me what the workaround was? As simply upgrading VIPM didn't work. Quote Link to comment Share on other sites More sharing options...
James McNally Posted January 22, 2019 Report Share Posted January 22, 2019 Same issue still in 2018 f2. Appears to be related to a vim in a class. Removing the vim from the class solves the problem. I got that work around from Tom and another at https://forums.ni.com/t5/LabVIEW/VI-Package-Manager-Fails-to-Build-with-Malleable-VIs-VIMs/td-p/3871468 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 22, 2019 Report Share Posted January 22, 2019 45 minutes ago, jamesmc86 said: Same issue still in 2018 f2. Appears to be related to a vim in a class. Removing the vim from the class solves the problem. I got that work around from Tom and another at https://forums.ni.com/t5/LabVIEW/VI-Package-Manager-Fails-to-Build-with-Malleable-VIs-VIMs/td-p/3871468 Hi @jamesmc86. Thanks for letting us know. I'd like to get this fixed, if possible. Would you be willing to put a very small/simple example .vipb project together and share it, so that we can easily reproduce and investigate? Thanks. Quote Link to comment Share on other sites More sharing options...
ThomasGutzler Posted November 20, 2019 Report Share Posted November 20, 2019 (edited) Here's an example I posted on lavag bits.zip Edited November 21, 2019 by ThomasGutzler Added attachment Quote Link to comment Share on other sites More sharing options...
ThomasGutzler Posted November 26, 2019 Report Share Posted November 26, 2019 Has anyone from JKI seen this? @Ashish @Jim Kring I thought there might be some interest in fixing this bug Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 17, 2020 Report Share Posted January 17, 2020 @ThomasGutzler @jamesmc86 @TomMcQ @hooovahh @drjdpowell We've been able to reproduce and fix this issue (ID 18605). It'll be fixed in VIPM 2020. Quote Link to comment Share on other sites More sharing options...
ThomasGutzler Posted January 19, 2020 Report Share Posted January 19, 2020 Excellent, Thanks @Jim Kring. Is there a planned release date for VIPM 2020? Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 20, 2020 Report Share Posted January 20, 2020 23 hours ago, ThomasGutzler said: Excellent, Thanks @Jim Kring. Is there a planned release date for VIPM 2020? Definitely before NIWeek in May 🙂 We do have a beta underway. Please LMK if you're interested to help test. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.