Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't check for migrations on Vitess yet #654

Merged
merged 1 commit into from Nov 21, 2018

Conversation

tirsen
Copy link
Collaborator

@tirsen tirsen commented Nov 20, 2018

No description provided.

import misk.logging.getLogger
import misk.resources.ResourceLoader
import org.hibernate.SessionFactory
import org.hibernate.query.Query
import java.sql.Connection
import java.util.*
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume we don't want to wildcard import right? Or do we alllow this in Kotlin?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so, I think some folks don't have the same java import rules setup for Kotlin in IntelliJ (myself included until recently).

@adrw
Copy link
Collaborator

adrw commented Nov 20, 2018

Rebasing off Master should restore green CI builds.

@tirsen tirsen force-pushed the jontirsen/2018-11-20/no-migration-check-vitess branch from fd5b392 to c486a9c Compare November 21, 2018 09:00
@tirsen tirsen merged commit f72a698 into master Nov 21, 2018
@tirsen tirsen deleted the jontirsen/2018-11-20/no-migration-check-vitess branch November 21, 2018 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants