Jim Kring
-
Posts
2,203 -
Joined
-
Last visited
-
Days Won
106
Posts posted by Jim Kring
-
-
7 hours ago, Horsechilli said:
Hi @Jim Kring, thank you!
Should I upload the dump of the crash report(?)
I just emailed you some instructions. I did this privately, since the steps involved are tricky and I don't want anyone trying this at home without a safety net.
-
1
-
-
Hi @Horsechilli
I saw this happen recently, too, and it was also in LabVIEW 2017.
I'll gather my notes on this to try to help you out. Stay tuned...
-Jim
-
1
-
-
Hi Jaun,
To fix this, can you try running this exe as Administrator (it should ask you to run as Administrator when you double click it):
"C:\Program Files (x86)\JKI\VI Package Manager\support\VIPM Update Registry.exe"
Please let me know if that helps.
-Jim
-
1
-
-
38 minutes ago, Sam Sharp said:
Hi Jim, I have also now run into a similar issue, I tried the steps in your workaround (with VIPM 2020.3) and it is looking for installer media here:
Hi Sam. I'm sorry for the trouble. This is really a pain...
Can you try using this copy of the "VI Package Manager Runtime Engine" installer?
>> vipm-2020.3.2540-windows-prerequisites.zip <<
This is a copy of the actual temp folder (containing the VIPM runtime engine) extracted during the VIPM 2020.3.2540 installation.
C:\Users\%USERNAME%\AppData\Roaming\JKI\VI Package Manager 2020.3\prerequisites
If that doesn't work, we could try the one from the 2020.3.2532 installer.
-
That’s great Tyler. I’m glad it worked for you and sorry for the trouble/delays. It’s been a bit bananas as we all transition back into office work.
-
1
-
-
I’m sorry the delay is impacting your CI pipeline. To remedy this you can immediately install the latest VIPM 2021 public beta. The next build of Dragon (coming shortly) will work with the VIPM 2021 public beta.
https://forums.vipm.io/topic/3784-vipm-2021-beta-download-and-getting-started/
-
1
-
-
2 hours ago, Joerg Hampel said:
Hey guys, I just tried to install this version (after uninstalling VIPM 2021) but it now reports that it has expired.
Is there a later version anywhere?
Thanks for reporting this. We will provide a new version shortly.
-
1
-
-
That's great!
If you're up for a little challenge, you could made the change to the source code on GitHub as a Pull Request.
https://github.com/JKISoftware/JKI-Simple-Localization
This would help ensure that future releases are compatible with your local modifications.
-
That's a great idea -- I don't think it's currently a supported feature.
It's definitely possible and I would probably do this (in the code) by adding a key for the additional axis labels:
yAxisLabel (maybe also allow yAxisLabel.0 and/or some kind of backward compatibility)
yAxisLabel.1
yAxisLabel.2The code is open source and you could take a look at how to do this.
-Jim
-
Hi @Sahithi
I think that, because of the way LabVIEW works, you will need to rebuild the package altogether.
-
One more thing...
Be sure to set up Basic Auth (username/password) protection (or limit access via VPN as you mentioned) if you’re going to let other people know your repository URL.
-
1
-
-
Hi Joerg,
Glad you figured this out. Yes, the protocol (https://) prefix needs to be included.
Also, I’m not sure if it’s related, but there’s one extra thing that might be relevant:
For HTTPS support in VIPM 2020.x be sure to set the network options in VIPM to “Use System Proxy Settings (Windows Only)”. The “No Proxy (Direct Connection)” setting doesn’t support HTTPS, yet...
In VIPM 2021 (now in beta) we’ve added HTTPS support in the default (No Proxy / Direct Connection) mode.
-Jim
-
This should be fixed in build 2746 -- I just tried to build the LabVIEW-Composition library and it seems to work.
You can get this latest build via check for updates in VIPM or here:
-
1
-
-
Hi there. This should be fixed in build 2746 -- I just tried to build the LabVIEW-Composition library and it seems to work.
You can get this latest build via check for updates in VIPM or here:
-
1
-
-
OK, we've found and hopefully resolved the issue. The fix will be in the next nightly beta build.
-
OK, we've found and hopefully resolved the issue. The fix will be in the next nightly beta build.
-
1
-
-
Thanks for posting these details.
We're able to reproduce the issue our end -- we'll will dig into it and report back here once we learn more.
-
Hi Antoine,
i’m so glad to hear you found the fix to this problem. I suspect the problem happened as a result of a botched update of LabVIEW by NIPM.
thank you for posting all of your details here. We will create a VIPM knowledge base entry and link to the NI knowledge base entry, in case anyone else runs into this.
thanks!
-
1
-
-
Hi Antoine,
I don't see an f4 patch available for download (e.g. on the LabVIEW Download Page). Can you point me to this update?
-
Sorry for the delay -- I wasn't getting email notifications of new posts to this forum 🤦♂️
I'll look into this right away. Thanks for your patience.
-
This setting marks that the package can only be installed into the global LabVIEW environment and not a virtual environment. If you want to know more, please sign up for the Dragon beta.
-
1
-
-
Sorry for the delay -- I wasn't getting email notifications of new posts to this forum 🤦♂️
I'll look into this right away. Thanks for your patience.
-
Oh, no! I'll see if I can get to the bottom of this.
Sorry for the delay -- I wasn't getting email notifications of new posts to this forum 🤦♂️
-
Hi There. Unfortunately, there's no `force` option when installing packages that would allow overriding the LabVIEW version compatibility.
Which package are you trying to install?
Missing dependencies
in JKI JSON
Posted
The easiest way is to save them into a VIPC file. This is a VIPM Pro feature, which we created to address this challenge.
How-to-use-VI-Package-Configurations (VIPC files)
However, I'm curios why the other dependencies can't be found -- is that a network issue?