LogMAN

Cross-post: Unable to download certain packages through VIPM - Application Builder, Installers and code distribution - LAVA

Does anyone else have trouble downloading certain packages through VIPM? For example, I'm unable to download SQLite Library 1.16.0 because "VIPM could not download the package ... from the remote server." I checked the error details and was able to locate the package on the server: https://download.ni.com/#evaluation/labview/lvtn/vipm/packages/drjdpowell_lib_sqlite_labview/ I tried different versions of VIPM, including 2019 and 2025.1 (build 2772) with no avail. Other packages do not appear to be affected. Can someone confirm? Edit: Should have mentioned that I'm able to download the package directly from the server with no issues so the problem is with VIPM.

Sure, you can specify the palette location using the browse button in VIPM.

Sorry for the late reply, I just saw your post on the package. Apparently I'm not automatically subscribed to topics created for my packages... I see you are using the snippet from the readme, which indeed is not updated. Thanks for bringing this to my attention, I'll have to fix that for the next releases. There are, however, many more examples included with the package which you can access from Example Finder (switch to directory view and look under PNR > lvssh2): Hope that helps! Edit: Added issues to address these points: Example in README is broken · Issue #28 · logmanoriginal/lvssh2 Make examples easier to discover · Issue #29 · logmanoriginal/lvssh2

There is a bug in VIPM 2024 Q3 that results in error 1003 when building a package in earlier versions of LabVIEW (2013 in my case) When opening the offending VI, a version conflict is reported: It appears that this particular VI was saved in LabVIEW 2019 at some point, breaking any callers. I was able to fix the issue on my end by re-saving the VI for LabVIEW 2009.

Cross-post: https://lavag.org/topic/22821-remove-block-diagram-after-build-with-vipm Please always include links when posting in multiple forums. This appears to be a potential bug in newer versions of VIPM. Here is a related topic:

I'm running VIPM BETA (build 2746), which shows an unusual average CPU load of 3-5% when the package manager is open and 10-15% when a package build specification is open. These values are a bit too high for my taste. A comparison with VIPM 2019 shows an average CPU load of 3-5% in both cases.

I have upgraded to the latest build 2746 and can confirm that it is working now 👍

Great job! Built 2746 properly disables the save button during the build process.

I did a few more tests and found that the build fails only when there is a accompanying .vipc file (even if that file does not specify any dependencies). Recreating the file does not fix the issue. The only workaround I found is to manually add dependencies. For comparison, here is a project for which the build succeeds (dependencies were added manually). https://bitbucket.org/drjdpowell/jsontext

So there is this new checkbox which isn't explained anywhere. What does it do?

You can clone the repositories from GitHub and try yourself: https://github.com/LogMANOriginal/LabVIEW-Composition https://github.com/LogMANOriginal/JSONtext-Object-Serialization I should probably mention that I'm using LabVIEW 2021 BETA (21.0b10) for the build.

Not sure if I'm doing something wrong, but the build process always fails for me and the error message is not helpful (see below). I have mass-compiled the project and found no broken VIs (build passes with VIPM 2019.0.0). Steps to reproduce Open a package build specification Press Build Package

The final message might be due to the build actually failing. I receive the same error when I don't try to break things.

Steps to reproduce Open package build specification Increment the package version (save button must be active - don't press it yet) Press Build Package Notice that the save button is active during the build process. Press Save Package Project The configuration is saved and the dialog will return to edit-mode (build process is still running). After a few seconds the build process fails with an error.