question-mark
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.

Improve Configuration's update result reporting

See original GitHub issue

Currently, Configuration’s update() method returns a boolean whether the update was successful or not. I feel there is some room for improvement here, for this method (or a relevant sibling method) to return more details about the update. Namely:

  • message/reason for the update failing (if any)
  • whether (or how many?) jars were actually updated, or there was nothing newer to get
  • what is the current version of the business application jar (The one defined in Maven’s <version /> In the business app I can get it by getClass().getPackage().getImplementationVersion())

That way updates could be logged and various feedback could be provided based on the update wizard (i.e. a popup displaying that a new version is now running, possibly linking to a change log).

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
mordechaimcommented, Mar 3, 2020

I’m considering actually returning a report object instead of boolean for the next release. What information do your think should it contain?

1reaction
mordechaimcommented, Mar 3, 2020

is that something I need to use for this purpose?

Yes, because the default handler isn’t configured to pass you that info. Unless if you want you can change the injected method call to:

@PostInject
private void getHandler(DefaultUpdateHandler handler) {
}

And then use reflection to get the context field; I’d recommend you against this approach though.

How do I call the update with both the update handler and the injectable

I assume you try to use the update overload that takes an UpdateHandler? In that case you can’t use injectable but you can still get all those info by directly reading that information from the instance itself.

Injectable can be used when the handler gets loaded by the service mechanism or by listing it in the config under <provider updateHandler=com.MyClass />

Perhaps tell me your general setup of the bootstrap so I can try to help.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Mastering Configuration Manager Patch Compliance Reporting
The following report should help you identify update problems within a specific collection and a group of systems and is designed to work...
Read more >
View a report on customizations and configuration changes
View a report on customizations and configuration changes · Navigate to All > Reports > View / Run and locate the Customer Update...
Read more >
Optimizing Remedy Smart Reporting performance
To configure restrictions for Remedy Smart Reporting query results, complete the following steps: Open the Usage Parameters panel.
Read more >
Configuration Settings (Tenable.sc 5.23.x)
Configuration Settings ; Scan Results. The number of days you want Tenable.sc to retain scan results. The default value of this option is...
Read more >
Global Advanced-Reports Settings - Qualtrics
Improve productivity. ... Results-Reports Breakouts · Global Results-Reports Settings; Visualizations ... Participant Import, Update, & Export Messages (EX).
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found