when installing a package which doesn't exist, commandbox claims forgebox is unreachable


I accidentally typed install cfconfig


Brad Wood
April 6, 2020, 7:46 PM

Thanks for the ticket, this has annoyed me for a while but I’ve just never cared enough to fix it. What happens is if ANY error is thrown from the forgebox wrapper, it’s caught and the “frogebox isn’t feeling well” error is shown. In most cases, errors from the forgebox wrapper are from HTTP connection issues, but obviously sometimes the forgebox wrapper throws errors for other reasons. Right now, any errors in ForgeBox simply throw an exception of type “forgebox” which is checked for explicitly in calling code. We’d probably need to create a new type of exception for this, or just throw a default exception. Alternatively, I could soften the message wording when a forgebox exception is thrown to simply say ForgeBox was unable to get the requested information. Really the root cause message is on the screen, so the current behavior really isn’t that big of a deal since if you just keep on reading, you’ll see exactly what the issue is. It’s more of a cosmetic change.

Brad Wood
July 28, 2020, 9:50 PM

I have re-worked the error message and put in an extra check so if the error detail is ‘The entry slug sent is invalid or does not exist' then we skip the artifacts check all together. It’s not as clean as a dedicated exception type, but it works a little better.



Brad Wood


Zac Spitzer



Affects versions

Fix versions