http://coldfusion.com logo
Join Slack
Powered by
On our build server, we are getting an error about...
# box-products
d
On our build server, we are getting an error about CommandBox not being able to install a specific version of a package that was recently published. When it errors, it lists the versions it sees (screenshot) so it is reporting back info from the package, but the newest version isn’t in the list. Locally, I can see the version no problem (1.2.1) via commandbox, install it, and I can see it on ForgeBox as well. https://forgebox.io/view/images-helper#versions. Any ideas what might be happening here?
Ok, I’m running 5.6.1 and I can’t reproduce this but a coworker who is running 5.5.2, which is the same as our build server, has the same problem. Why would a minor version change in commandbox not allow the install of a patch version change in a package?
b
Chances are something is cached in forgebox
You can check what version you see with
Copy code
forgebox show package-name
I see version 1.2.1 when I run that
Were there any errors when you pubished?
I had this issue just a couple days ago where the API errors out while publishing, and even though it did publish successfully, the caches were not cleared like normal.
d
Right, running that forgebox show command gives different results on 5.6.1 vs 5.5.2.
b
That's interesting-- I don't think we've changed the API URL that's hit in a very long time.
This SHOULD be the URL getting hit https://forgebox.io/api/v1/entry/images-helper
Which you can hit in your browser and see the versions in the JSON
Our ForgeBox cache is stored in Couchbase, so it should be cached between all our docker containers.
Meaning if it's cached for one person, it's cached for everyone.
However, one likely scenario is you are logged into forgebox with different API tokens, which could affect what cached data you see
The caches will clear eventually, but I just pushed some cache clear buttons in our ForgeBox admin to see if that helps
I'm still curious the answer to my question above about whether your publish had any errors
d
In a meeting but will update you in a few minutes.
👍 1
A different coworker had a collection error when he tried to publish on 5.5.2. He doesn’t still have the exact error or I’d share it. He’s since upgraded CommandBox.
b
Yep, that's the reason
And it's not related to CommandBox
It's a Hibernate issue in ForgeBox
The error leaves ForgeBox's cache un-cleared
cc/ @Javier Quintero
I'm guessing one or both of you are logged into forgebox, and the API token gives you different cache prefixes (since you could have access to different packages)
d
I was logged in via the cli right before that. My coworker was not. So that could be what is going on.
b
Yeah, because your API calls to forgebox include your API key, but your coworker's API calls don't
d
So that seems like a bug, right?
b
And forgebox takes API key into account when caching
What seems like a bug?
The Hibernate error that prevented the caches from clearing is a known issue @Javier Quintero is working on.
But the fact that you have different cached data is totally normal
Imagine if you have private packages that only you have access to. Obviously, no-one else can share your cache!
d
Our build server, which is not logged into forgebox, should’ve been give the most recent version. That’s the bug. Sounds like that is what you’re referring to with the hibernate error.
Different cached data seems totally fine, but they should be busted as needed to give the correct version data.
b
Yes, obviously, lol
As I said, this is a known issue @Javier Quintero is working on, which is why I asked if you had errors while publishing way back up at the start of this thread
👍 1
3 Views
Open in Slack
PreviousNext
Powered by