I have been getting this in my logs. Thoughts?
What's the app?
That's HPM, but all of those can't be bad. @csteele thoughts?
2 Likes
1 Like
HPM updated recently. Is that the cause?
What version of HPM are you running? My guess is 1.9.7
I think this is related to some code additions i made for HPM recently. I have already made additional changes to some test code and submitted it to @csteele to be merged. This is related to a effort to improve Beta version support.
The last change was to allow individual selection of what packages are activated, but i missed a problem in my testing. It has been resolved in the latest version once it gets merged.
2 Likes
I was mostly interested in what the App was linked in the logs, but based on your comment and @thebearmay 's, likely to be at least linked to HPM, if not caused by HPM itself.
@mavrrick58 's question about the HPM version is likely the issue....
Yep. Version 1.9.7
1 Like
If you want to temporarily fix it until the next update perform the following steps.
- Go into the HPM Settings menu and save the options at the bottom.
- Then go into the code for HPM and scroll down to line 4254. You should see this
def shouldInstallBeta(item) {
if (pkgBetaOn != null) {
return item.betaLocation != null && pkgBetaOn.contains(item.name)
}
}
def getItemDownloadLocation(item) {
if (pkgBetaOn != null) {
if (item.betaLocation != null && pkgBetaOn.contains(item.name))
return item.betaLocation
}
return item.location
}
Replace it with
def shouldInstallBeta(item) {
return item.betaLocation != null && includeBetas
}
def getItemDownloadLocation(item) {
if (item.betaLocation != null && includeBetas)
return item.betaLocation
return item.location
}
That effectivly reverts that block of code to what it was in 1.96. It makes the beta selection in the preferences mean nothing, but it will get it working for you if you are worried about updates.
Sorry for the inconvience. This will be fixed in the next batch of code which we are already testing now.
4 Likes
So what's the crux of the problem...?
Oh, beta...
Not a problem at present. Just noticed the log entries. I will await the HPM update. Thanks for the help.
I also see the same logs... you are more observant than me @Pantheon ... 
1 Like
With those two methods specifically it has to do with how HPM manages Packages vs individual drivers, apps, bundles. The addition i made worked for full packages, but fell on it's face once you tried to work with a particular driver, app, or bundle by itself. It has to do with how it matches everything. I am not sure how it got through my testing, but it did. To say the least i am doing a fair amount more testing with the latest code drop.
I had to create a whole new routine that will build the list of items that the beta package selection includes. That will be used for those routines going forward for the comparison. I also had to do a better job of working with object that are null to prevent failures. We actually released a quick patch after the intial release to address that.
Yea. Trying to make it more useable as prior to 1.9.6 it was very limited. App owners only had one Release notes for both Beta and Stable. If you turned Beta on for one app you turned it on for everything you had installed through HPM
The improvements made for beta are
- Added the ability to have seperate release notes (1.9.6)
- Added the option to select which package gets installed (1.9.7 kind of) which in turn means it isn't a all or nothing setting.
- Added the ability to enable beta at install time time (1.9.8)
Those are the main things for each release of HPM related to beta. There are some other cosmetic stuff as well.
4 Likes
I've been meaning to start using a beta branch in my repos, thanks for working with @csteele on this... and thanks to @csteele ... as always...
1 Like
Feel free to join the conversation about Beta enhancements in the below thread if you have suggestions. Now the conversation has started to shift about how to inform developers about how to use it best.
1 Like
Thanks for making HPM "beta" 
You just need to Repair HPM from within HPM. 
The code @mavrrick58 posted is already applied to v1.9.7 BUT anyone that upgraded in the first couple of hours, needs to do the Repair. Anyone upgrading after those first couple of hours get the fixed code automatically.
One can look at the code , Line 4254 at:
and see that the code (above) has already been applied.
If you see 100% the dreaded "Skipping bad manifest..." then you need to Repair HPM, that's it.
The Repair was advised in the original Topic:
4 Likes
@Pantheon also make sure you are not using beta at all. Make sure in the preferences that no packages are selected and that the option to install betas is turned off.
1 Like
go into Un-Match a Package and select both HPM entries.. then click Next... it will fix itself right up. HPM is the only Package HPM manages without having to select it explicitly stands to reason then, that it knows how to manage itself.
2 Likes
