MikeLud1
IPCT Contributor
5.9.9 - January 17, 2025 - More Pre-6.0 feature releases
- Thread starter jaydeel
- Start date
5.9.9.73
The highlights are mine. Some interesting DB-related items.
[5.9.9.73] – 2025-08-28
Added
• N/A
Fixed
• Web request actions containing :/ incorrectly deleted everything in the URL before this. The intention is only to remove the protocol specification (e.g., http://) if it occurs at the beginning of the path.
Changed
• UI3 updated to version 300
• You may need to uninstall and then re-install the CodeProject.AI in order to continue to receive notice of updates or to install modules, as the developers have moved the project to a GitHub.io site.
• Further to discovering possible bug/s when regenerating a large DB (>250,000 records), specific corruption position and error information are written to the log during the ReIndex phase. The ReIndex phase may also no longer be cancelled due to shutdown once it has started to prevent potential data sync issues.
• Following complaints of the DB Regenerate hanging or not finishing properly, removal of code that read clip .DAT files during a full DB regeneration that was designed to repopulate the alert list in the absence of alert JPEG files. A full review of the DB methods is now underway and we will likely see a major revamp in a further pre-6.0 release.
The highlights are mine. Some interesting DB-related items.
[5.9.9.73] – 2025-08-28
Added
• N/A
Fixed
• Web request actions containing :/ incorrectly deleted everything in the URL before this. The intention is only to remove the protocol specification (e.g., http://) if it occurs at the beginning of the path.
Changed
• UI3 updated to version 300
• You may need to uninstall and then re-install the CodeProject.AI in order to continue to receive notice of updates or to install modules, as the developers have moved the project to a GitHub.io site.
• Further to discovering possible bug/s when regenerating a large DB (>250,000 records), specific corruption position and error information are written to the log during the ReIndex phase. The ReIndex phase may also no longer be cancelled due to shutdown once it has started to prevent potential data sync issues.
• Following complaints of the DB Regenerate hanging or not finishing properly, removal of code that read clip .DAT files during a full DB regeneration that was designed to repopulate the alert list in the absence of alert JPEG files. A full review of the DB methods is now underway and we will likely see a major revamp in a further pre-6.0 release.
Yikes, who wants to go first on that point? Past experiences have left a somewhat poor impression of that process, and I tend to want to "leave well enough alone" for the time being. Has anyone done a full un-install and re-install recently (since they moved the project to the new Github site)?
IReallyLikePizza2
Known around here
I'm confused, why is there CodeProject AI changelog in the BI Changelog? They are 2 completely separate applications
Within the BI interface, under the settings tab for Blue Iris News and Updates, the lower portion of that window also informs you if your CodeProject AI installation is also up to date. This is likely broken unless your CPAI installation is sourced from the current Github site, not the older original CodeProject site (which is no longer active/supported).
IReallyLikePizza2
Known around here
CPAI was not an issue, it just keeps working.
Well, to answer my own question: I just went through the upgrade routine, first from BI 5.9.9.72 to 5.9.9.73. No problems there to report, other than the bottom of News and Updates tab/window for CPAI being completely blank post-upgrade (somewhat expected, based on release notes). Then I took the plunge and uninstalled CPAI 2.9.5.0 (the original version, from the old website), and reinstalled the "new" version of CPAI 2.9.5.0 from the Github site, which installed with no issues for me. Now BI does correctly report that my CPAI version is "the current version" (which I believe it also did on previous versions of BI, such as 5.9.9.72). Meh...nothing lost, and not much gained other than the apparent ability for BI to again keep track of whether CPAI is up to date.