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

Upgrade sbt launcher script (sbt-extras) #225

Merged
merged 3 commits into from
Jul 24, 2015

Conversation

isnotinvain
Copy link
Contributor

No description provided.

@isnotinvain
Copy link
Contributor Author

Actually, this PR updates the sbt launcher, and tells travis to use it -- we don't have to do that, we're currently using whatever sbt is preconfigured in the travis environment, which I assume will be fixed soon: https://twitter.com/travisci/status/621055235038035968

@johnynek
Copy link
Collaborator

looks like there is some escaping bug here. Legit failure.

@isnotinvain
Copy link
Contributor Author

what do you think about the previous comment though? this build wasn't using the ./sbt at all, it was using the pre-installed sbt

@johnynek
Copy link
Collaborator

Well, the problem with using their installed sbt is that we are at their mercy, and we are not testing how we develop locally or how our contributors might use sbt. I think it is nicer to have the only dependency be a jvm, otherwise we will have to support a lot of sbt issues for new contributors.

So, I'd rather standardize on the launcher being in the state of the repo.

@isnotinvain
Copy link
Contributor Author

yeah sgtm, i'll try to fix this one

@isnotinvain
Copy link
Contributor Author

OK, think it's fixed. Looks like a property test found a bug though:

[info] - UUID -> String
[info] - URL -> String *** FAILED ***
[info]   IllegalArgumentException was thrown during property evaluation.
[info]     Message: invalid host wildcard specification
[info]     Occurred when passed generated values (
[info]       arg0 = http://鷕ﺌ遦ꆙ諪玄饆ᙆ䊡⺓壑著錮쾠䗚㧪ى᭲岻㒾픷挵壨頛㚚‛ᾍ䲊椄ᄀ뒾葊쟿旬䌡㝖俶펪佩昏᜞狖嘲僀ãꗷⶈ㢊ᗽ㫋*Ꞝ梞⬚츙.com
[info]     )

@isnotinvain
Copy link
Contributor Author

looks like it might be the *

@johnynek
Copy link
Collaborator

We should fix that test. It does fail with randomly generated unicode, which is not a good way to generate URLs.

johnynek added a commit that referenced this pull request Jul 24, 2015
@johnynek johnynek merged commit 8d9b01a into develop Jul 24, 2015
@johnynek johnynek deleted the alexlevenson/sbt-launcher-upgrade branch July 24, 2015 01:18
@isnotinvain
Copy link
Contributor Author

I've been trying (and failing) to find a string that repros this. Copying the above example doesn't seem to work (probably something is lost in the copy)

@isnotinvain
Copy link
Contributor Author

the odd thing is we do Try(new Url(_)), and the only other method called on this object is .toString. the error "invalid host wildcard specification" comes from here: https://github.com/openjdk-mirror/jdk/blob/jdk7/jdk7/master/src/share/classes/java/net/SocketPermission.java#L425 but I don't yet see why / how we end up there

@isnotinvain
Copy link
Contributor Author

seems like you get there by a) having a security manager and b) calling openConnection -- I don't know why we'd be doing b, and maybe a) has to do with travis setting one up?

@isnotinvain
Copy link
Contributor Author

turns out URL.java is pretty complicated :/

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

2 participants