Using dropwizard-migrations: Could not find implementation of liquibase.logging.Logger - liquibase

I'm getting a pretty odd exception that I can't figure out the cause of. When I run a db status, I get:
Caused by: liquibase.exception.ServiceNotFoundException: liquibase.exception.ServiceNotFoundException: liquibase.exception.ServiceNotFoundException: Could not find implementation of liquibase.logging.Logger
at liquibase.logging.LogFactory.getLogger(LogFactory.java:19)
at liquibase.logging.LogFactory.getLogger(LogFactory.java:30)
at liquibase.database.DatabaseFactory.findCorrectDatabaseImplementation(DatabaseFactory.java:67)
at liquibase.Liquibase.<init>(Liquibase.java:52)
at com.yammer.dropwizard.migrations.ManagedLiquibase.<init>(ManagedLiquibase.java:47)
at com.yammer.dropwizard.migrations.AbstractLiquibaseCommand.run(AbstractLiquibaseCommand.java:39)
at com.yammer.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:58)
at com.yammer.dropwizard.cli.Cli.run(Cli.java:53)
at com.yammer.dropwizard.Service.run(Service.java:61)
at com.derp.SomeService.main(SomeService.java:27)
... 6 more
Caused by: liquibase.exception.ServiceNotFoundException: liquibase.exception.ServiceNotFoundException: Could not find implementation of liquibase.logging.Logger
at liquibase.servicelocator.ServiceLocator.newInstance(ServiceLocator.java:179)
at liquibase.logging.LogFactory.getLogger(LogFactory.java:17)
... 15 more
Caused by: liquibase.exception.ServiceNotFoundException: Could not find implementation of liquibase.logging.Logger
at liquibase.servicelocator.ServiceLocator.findClass(ServiceLocator.java:145)
at liquibase.servicelocator.ServiceLocator.newInstance(ServiceLocator.java:177)
... 16 more
I'm not sure how to resolve it. Googling a bit, it seems to be a somewhat intermittent problem that has, in the past, yielded bugfixes in Liquibase. I didn't expect this to happen in such an integrated feature. I am using dropwizard-core/hibernate/migrations 0.6.2. I'm using the com.smokejumperit.gradle.OneJarPlugin gradle plug-in to package it all up, which I think is also responsible for class loading.
Anyway, I'm at a bit of a loss. Any ideas? Anyone seen this before?

Related

Optaplanner Score Corruption Using Bavet

java.lang.IllegalStateException: Score corruption ([30]hard/[0/30]soft): the workingScore (-3init/[-1850]hard/[-1/-1190]soft) is not the uncorruptedScore (-3init/[-1880]hard/[-1/-1220]soft) after completedAction (TWC(20301005) {TWC(20301008) -> TWC(20301008)}):
Hello, I got this error when running Vehicle Routing Solution. I didn't know what is the meaning of after completedAction (TWC(20301005) {TWC(20301008) -> TWC(20301008)}):.
TWC is TimeWindowCustomer, and have previousStandstill. But why Optaplanner change into same PlanningEntity TWC(20301008) -> TWC(20301008) ?
Let's leave aside the move itself - the reason why such a useless move is being executed is probably a bug. But even then there shouldn't be a score corruption; it's just an inefficient behavior.
If, when you use the default constraint stream implementation (DROOLS), the score corruption disappears, please file a bug report for us, with some code we can execute to reproduce the problem. Make sure you are using the latest version of OptaPlanner.
If the problem is still there even when using DROOLS, the problem is likely in your domain model.

How can i solve the Array problem in Kotlin?

When I try to compile some basic array code I get errors. I tried to re-install IntelliJ and I made all updates.
fun main(args: Array<String>) {
val numbers = intArrayOf(1, 4, 42, -3)
if (4 in numbers) {
println("numbers array contains 4.")
}
}
Here are the errors.
Exception in thread "main" java.lang.NoClassDefFoundError: kotlin/KotlinPackage
at KtlneKt.main(ktlne.kt:2)
at KtlneKt.main(ktlne.kt)
Caused by: java.lang.ClassNotFoundException: kotlin.KotlinPackage
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 2 more
Process finished with exit code 1
Same question. So same answer: I had the same problem and I discovered that this is a bug of Kotlin library. You cannot call intArrayOf() method.
I am sure that you are using Windows 10 Single Language Turkish. (I was using the same operating system.) Kotlin's some libraries cannot work on Turkish operating system. You can check this issue on YouTrack.
You can solve your problem with installing Windows 10 Pro English or Windows 10 Single Language English. I do not know any other approach right now. (You can open new issue on Kotlin website.)
This bug took from me 30 days. You can check my related question about this Kotlin bug.

Android studio error in design tab

I am currently learning Kotlin through a Udemy course for Android Development and I cannot proceed with the course unless I fix all the problems I'm having. One of these problems is Failed To Instantiate one or more classes
It gives a detailed description saying:
The following classes could not be instantiated:
- android.support.v7.widget.ActionBarContainer (Open Class, Show Exception, Clear Cache)
- android.support.v7.widget.ActionBarContextView (Open Class, Show Exception, Clear Cache)
- android.support.v7.app.WindowDecorActionBar (Open Class, Show Exception, Clear Cache)
Tip: Use View.isInEditMode() in your custom views to skip code or show sample data when shown in the IDE. If this is an unexpected error you can also try to build the project, then manually refresh the layout. Exception Details java.lang.ClassNotFoundException: android.view.View$OnUnhandledKeyEventListener
I am new to Kotlin and Android Studio so there are a lot of things that I don't understand, I tried doing something in the Gradle but it just closed or crashed(I'm not really sure)Android Studio and I had to reopen it.
Make sure that you have this line in gradle (Module:app)
implementation 'com.android.support:appcompat-v7:27.1.1' or later
then
Build/Clean Project
Build/Rebuild Project
and if necessary
File/Invalidate Caches / Restart

Titan storage.backend=inmemory Causes Incompatible Data Type Exception

I've been using titan-cassandra storage.backend=cassandra in my testing environment and recently learned that I can simply plop in storage.backend=inmemory to test with an in-memory graph. As this will drastically increase the speed of the hundreds of tests - this sounds great. But, making this change to my otherwise simple test configuration causes many of my once passing tests to fail. Here's my configuration:
storage.backend=inmemory
storage.hostname=localhost
storage.cassandra.keyspace=test
There are two errors that come up, the vast majority being:
java.lang.IllegalArgumentException: Incompatible data types for: variable
while much less commonly:
com.thinkaurelius.titan.core.TitanException: Could not commit transaction due to exception during persistence
Any idea on how I can resolve these issues?
I do my tests using in memory graph database too. While, I don't specify anything for hostname, I tried using, now, localhost, and it still works. I believe the problem might be somewhere else and you have fixed it by now.

Portland group FORTRAN pgf90 program fails when compiled with -fast, succeeds with -fast -Mnounroll

This code hummed along merrily for a long time, until we recently discovered an edge case where it fails silently-- no errors returned.
The fail is apprently pretty subtle. We can get the code to run uneventfully in the edge case by:
1) compiling with any set of options that includes -traceback or debug (-g or -gopt);
2) compiling with -fast -Mnounroll;
3) compiling with optimization <2;
4) adding WRITE statements into the code to determine the location of the fail;
In other words, most of the tools useful for debugging the failure-- actually result in the failure disappearing.
I am probing for any information on failures related to loop unrolling or other optimization, and their resolution.
Thank you all in advance.
I'm not familiar with pgf (heck, it's been 10 years since I used any fortran), but here are some general suggestions for tracking down (potential) compiler bugs:
Simplify a reproducible case. I.e. try to reproduce the problem with a similar looking piece of code that has all the superfluous details removed. This is helpful because a) you'll be less hesitant to release the code publicly, and b) if someone attempts to diagnose the problem, it will be easier for them with less surrounding material.
Talk to the experts: If you have a support contract for pgf, use it! There's a support request form on their site. If not, there's a User Forums section where you might be able to post your information - someone else may have better workaround, or an employee there may be able to log your problem.
Double-check your code. Is it possible that you're relying on some sort of unspecified behavior? This is the sort of thing that would cause your program to switch behavior when changing optimization levels. I'm not saying compiler bugs are impossible, but it could be a hack in your code too.
Hope that's helpful.