ThomasGutzler Posted November 18, 2019 Report Share Posted November 18, 2019 (edited) Hi, I'm having problems building a vipc from a vipb with files containing nested vims. Getting the following error from VIPM: ERROR: 7: VIPM API_vipm_api.lvlib:Parse Build Return Message_vipm_api.vi<ERR> Code:: 7 Source:: 0053C289D635723F5DC0A4F08297566A<ERR> The following source VIs or Libraries are missing. Please correct this problem before rebuilding. b39afad9-8321-4719-86a9-dddab325fc87.vi The following source VIs or Libraries are the callers of missing files BitsSetter.vim I created a zip with the vims and the vipb file. Any suggestions how to fix this? Opening the files shows no errors. Replacing the nested vim with its actual implementation fixes the problem but I don't want to give in just yet. I'm on LV 18.0.1f4 64bit with VIPM 2018.0.0f1 Cheers bits.zip Edited November 20, 2019 by ThomasGutzler 1 Quote Link to comment
ThomasGutzler Posted November 19, 2019 Author Report Share Posted November 19, 2019 (edited) Minor update, I've gotten rid of the different type cases by doing this While that makes the code prettier, it also prevents it from building into a vipc due to the same issue: nested vims Edited November 20, 2019 by ThomasGutzler Quote Link to comment
ThomasGutzler Posted November 20, 2019 Author Report Share Posted November 20, 2019 I made a new .zip with the current versions of all files. Would be cool if someone else with a VIPM pro would try to build this just to check if it's my problem. Cheers bits.zip Quote Link to comment
TomOrr0W Posted November 20, 2019 Report Share Posted November 20, 2019 @drjdpowell was able to build a VIPM package that uses nested VIMs. See https://lavag.org/topic/21268-malleable-buffer-seeing-what-vims-can-do/ Quote Link to comment
TomOrr0W Posted November 20, 2019 Report Share Posted November 20, 2019 (edited) I get the same errors as you in both LV2019 SP1 64-bit and LV2019 SP1 with VIPM 2019.0.0. Edited November 20, 2019 by TomOrr0W Quote Link to comment
TomOrr0W Posted November 20, 2019 Report Share Posted November 20, 2019 It looks like the issue is putting nested VIMs in a class. See https://forums.jki.net/topic/2641-vi-calling-vim-fails-to-build-fixed-in-vipm-2017f1/ and https://forums.ni.com/t5/LabVIEW/VI-Package-Manager-Fails-to-Build-with-Malleable-VIs-VIMs/td-p/3871468. @Jim Kring If you are still looking for a simple reproducing case of this bug, here is one. Quote Link to comment
ThomasGutzler Posted November 21, 2019 Author Report Share Posted November 21, 2019 Good find! @Jim Kring happy to assist in any way I can when you're looking into this bug. Quote Link to comment
ThomasGutzler Posted December 4, 2019 Author Report Share Posted December 4, 2019 Unfortunately, nobody seems to care about this any more Even with the newly provided example Quote Link to comment
JKSH Posted December 4, 2019 Report Share Posted December 4, 2019 On 11/21/2019 at 10:01 AM, ThomasGutzler said: Good find! @Jim Kring happy to assist in any way I can when you're looking into this bug. Jim does not come to LAVAG often (e.g. see https://lavag.org/topic/21017-where-are-openg-product-pages-for-packages/?do=findComment&comment=129287 ) I'd imagine you'd get a lot more interest if you post at the JKI forums 13 minutes ago, ThomasGutzler said: Unfortunately, nobody seems to care about this any more Nested malleables + VIPC is not a combo that I use Quote Link to comment
ThomasGutzler Posted December 5, 2019 Author Report Share Posted December 5, 2019 4 hours ago, JKSH said: Jim does not come to LAVAG often I'd imagine you'd get a lot more interest if you post at the JKI forums I replied with an example on the relevant thread on the JKI forum Quote Link to comment
TomOrr0W Posted December 5, 2019 Report Share Posted December 5, 2019 (edited) 19 hours ago, ThomasGutzler said: I replied with an example on the relevant thread on the JKI forum You might want to post a link to this thread in that thread. The attachment is listed as unavailable - the error message says "This attachment is not available. It may have been removed or the person who shared it may not have permission to share it to this location". Brian's original attachment is also listed as unavailable. Maybe that was JKI's problem all along - they wonder why no one sends them examples while not realizing that they don't allow anyone to post code. Edited December 5, 2019 by TomOrr0W Quote Link to comment
ThomasGutzler Posted December 5, 2019 Author Report Share Posted December 5, 2019 17 minutes ago, TomOrr0W said: The attachment is listed as unavailable - the error message says "This attachment is not available. It may have been removed or the person who shared it may not have permission to share it to this location". Brian Hoover's original attachment is also listed as unavailable. I can download them both. Maybe you need to have an account for the download to work. I had to create an account to be able to upload. Quote Link to comment
hooovahh Posted December 9, 2019 Report Share Posted December 9, 2019 On 12/5/2019 at 4:14 PM, TomOrr0W said: Brian's original attachment is also listed as unavailable. I also can redownload it, you likely need an account. Quote Link to comment
ThomasGutzler Posted January 20, 2020 Author Report Share Posted January 20, 2020 Here we are. JKI (Jim) says: Quote We've been able to reproduce and fix this issue (ID 18605). It'll be fixed in VIPM 2020. Yay 1 Quote Link to comment
Jim Kring Posted January 20, 2020 Report Share Posted January 20, 2020 We've been able to reproduce and fix this issue (ID 18605). It'll be fixed in VIPM 2020. You can follow this thread on JKI's forums. Quote Link to comment
Jim Kring Posted February 15, 2020 Report Share Posted February 15, 2020 VIPM 2020 Beta is now available - sign up here: https://forums.jki.net/topic/3082-vipm-2020-beta-sign-up-is-now-open/ Quote Link to comment
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.