Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Notification publisher configuration cannot be read after upgrade from 3.8.0 to 4.1.0

See original GitHub issue

Current Behavior:

After migrating from 3.8.0 to 4.1.0 the notification publisher configuration in NOTIFICATIONRULE.PUBLISHER_CONFIG cannot be read by the application (at least for the email publisher). In 3.8.0 this is stored as a large object in the database while 4.1.0 stores it directly in the column. Other large objects like license texts or vulnerability descriptions work.

Steps to Reproduce:

Setup a database and configure an email notification with destination address with 3.8.0
Run the migration script
Run the 4.1.0 API server

Expected Behavior:

I expect the configuration to be read and visible in the frontend.

Environment:

Dependency-Track Version: 4.1.0
Distribution: Executable WAR
BOM Format & Version:
Database Server: PostgreSQL
Browser: Firefox

Issue Analytics

State:
Created 3 years ago
Comments:11 (4 by maintainers)

Top GitHub Comments

3reactions

dfn-certlingcommented, Mar 18, 2021

Digging deeper I discovered another problem with the CLOBs and PostgreSQL. The extension lo provides as a rationale that the JDBC driver assumes that BLOBs are stored in the tables. Modifying or deleting them is assumed to remove the large object. In the database, however, large objects are separate entities that are just referenced from the tables and have to be deleted separately. Otherwise they just remain as unreferenced objects in the database. Indeed I see this for the CLOB columns in our installation. Therefore switching to storing these in the table seems to be the most sensible choice to me.

This affects the following columns from Dependency-Track and one from Alpine:

AnalysisComment.comment
NotificationRule.publisherConfig
Vulnerability.description, .recommendation, .references, .credits
Permission.description

The CLOB columns for NotificationPublisher.template and License.text, .template, .header, .comment are resynchronized on system start and thus automatically converted from their CLOB representation.

The pull request should rewrite the necessary columns and remove all large objects to also remove the orphaned ones.

0reactions

github-actions[bot]commented, Aug 26, 2021

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Top Results From Across the Web

Release notes & updates – Azure CLI - Microsoft Learn

Learn about the latest Azure Command-Line Interface (CLI) release notes and updates for both the current and beta versions of the CLI.

Change Log - Dependency-Track

Upgrade Notes: The value of the scanner.analysis.cache.validity.period configuration property will be reset to 12 hours during the automated upgrade.

Blog - Apache Cordova

By passing down all attribute data, Cordova-Common no longer needs to be updated for adding and supporting new platform attributes.

Firebase Apple SDK Release Notes - Google

Added notification support for iOS 16 simulators on Xcode 14. ... Updated GTMSessionFetcher dependency specifications to enable support for the compatible ...

Docker Compose release notes

Updated Docker Engine API to restore compatibility with Golang 1.18 needed ... Added ssh config to the build options when building an image...